-
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
Teradata Connector #16373
Teradata Connector #16373
Conversation
The Python checkstyle failed. Please run You can install the pre-commit hooks with |
2 failed tests on run #34268 ↗︎Details:
|
Test | Artifacts | |
---|---|---|
Services detail page > Database Service page > GlossaryTerm assign, update & delete |
Screenshots
Video
|
|
Services detail page > Database Service page > Soft delete |
Screenshots
Video
|
Review all test suite changes for PR #16373 ↗︎
hi @gpby, thanks a lot for the contribution! Appreciate the effort! A couple of comments here:
Thanks! |
|
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.
Thanks @gpby, this LGTM. We can add the docs to another PR. Appreciate the effort
|
|
* [WIP] add teradata connector * [WIP] add teradata ingestion * [WIP] add teradata connector * [WIP] add teradata connector * [WIP] add teradata connector * [WIP] add teradata connector * [WIP] add teradata connector * [WIP] add teradata connector * Reformat code * Remove unused databaseName property (cherry picked from commit d909a31)
Supporting Teradata Vantage:
Fixes #15756
Here is a beta version of Teradata Database / Teradata Vantage Connector
It supports only Metadata and Profiler ingestion
Known limitations:
Type of change:
Checklist:
I have read the CONTRIBUTING document.
My PR title is
Fixes 15756: Support Teradata Connector
I have commented on my code, particularly in hard-to-understand areas.
For JSON Schema changes: I updated the migration scripts or explained why it is not needed.
The issue properly describes why the new feature is needed, what's the goal, and how we are building it. Any discussion
or decision-making process is reflected in the issue.
I have updated the documentation.
I have added tests around the new logic.