-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Tableau: Add ability to force parsing of Custom SQL #9841
Comments
Merged
5 tasks
This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tableau is not good at parsing of custom SQL queries even those that are marked as supported, so if we build table/column level linage blindly relying on metadata returned by Tableau server, the resulting linage graph is far from what is expected:
Experiments with sqlglot based parser of SQL queries used by DataHub gives much better results. But the problem is it is used only for cases when Tableau was unable to parse Custom SQL query on its own and did not return upstream tables metadata.
Could you implement an option allowing to force parsing of Custom SQL queries and ignoring upstream tables metadata provided by Tableau?
The fix is by the link:
#9838
See the feature
force_extraction_of_lineage_from_custom_sql_queries: true | false
The text was updated successfully, but these errors were encountered: