You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Unable to see our ADB unity catalog's lineage in purview portal
To Reproduce
Steps to reproduce the behavior:
Followed the instructions as per the 'connector only deployment' process.
Expected behavior
To view ADB(Unity Catalog) lineage in purview.
Logs
encountered this error during post-installation steps (creating a custom type definition through API):
{"requestId":"xxxx","errorCode":"ATLAS-400-00-01A","errorMessage":"invalid parameters: invalid payload, expect schemaAttributes in purview_custom_connector_generic_column should be list of string, but found: data_type"}
Screenshots
The text was updated successfully, but these errors were encountered:
I had the same issue and, after looking into "deployment/infra/Custom_Types.json" file and Apache Atlas documentation found a fix.
Just change "schemaAttributes": "data_type" to "schemaAttributes": "[\"data_type\"]".
Hope that solves the problem!
Describe the bug
Unable to see our ADB unity catalog's lineage in purview portal
To Reproduce
Steps to reproduce the behavior:
Expected behavior
To view ADB(Unity Catalog) lineage in purview.
Logs
encountered this error during post-installation steps (creating a custom type definition through API):
{"requestId":"xxxx","errorCode":"ATLAS-400-00-01A","errorMessage":"invalid parameters: invalid payload, expect schemaAttributes in purview_custom_connector_generic_column should be list of string, but found: data_type"}
Screenshots
The text was updated successfully, but these errors were encountered: