-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add Teradata connector docs #16672
Add Teradata connector docs #16672
Conversation
Hi there 👋 Thanks for your contribution! The OpenMetadata team will review the PR shortly! Once it has been labeled as Let us know if you need any help! |
To deploy OpenMetadata, check the Deployment guides. | ||
{%/inlineCallout%} | ||
|
||
Connector was tested on Teradata DBS version 17.20. Since there are no significant changes in metadata objects, so it should work with 15.x, 16.x versions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gpby can we document what are the user permissions one needs to setup to get the metadata from Teradata?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By default all Teradata users has access to metadata objects (dbc.tablesv, dbc.columnsv, etc.) because public role has access to those objects. So DBA should do some explicit revokes to limit access to metadata object (e.g. KB0024146)
|
1 failed test on run #34406 ↗︎Details:
|
Test | Artifacts | |
---|---|---|
Superset Ingestion > Create & Ingest Superset service |
Screenshots
Video
|
Describe your changes:
As discussed in PR #16373 documentation for Teradata Connector has been added.
Type of change:
Checklist:
Fixes <issue-number>: <short explanation>