Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to see the catalog's lineage details in purview portal, for connector only deployment option #239

Open
kunr0747 opened this issue Jun 18, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@kunr0747
Copy link

Describe the bug
Unable to see our ADB unity catalog's lineage in purview portal
image

To Reproduce
Steps to reproduce the behavior:

  1. Followed the instructions as per the 'connector only deployment' process.

Expected behavior
To view ADB(Unity Catalog) lineage in purview.
image

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

socket_exception
@kunr0747 kunr0747 added the bug Something isn't working label Jun 18, 2024
@rvalente-bi4all
Copy link

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!

@davidkhala
Copy link

pending merge of #235

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants