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
Imagine we have an unsupported (by Tableau) Custom SQL query like this:
id = c00a497c-2d83-4fd7-b259-35eb54f4d97d
SELECT
t1.col1
t1.col2
FROM
t1
It will parse SQL query and infer that the Custom SQL id = c00a497c-2d83-4fd7-b259-35eb54f4d97d is referencing upstream table t1, and its columns col1, col2. It will save table linage and fine-grained linage information for the Custom SQL entity.
But it does not emit the parsed tables itself (doesnot matter if ingest_tables_external was enabled or not), for those who has no ability to pre-ingest the tables, the linage will not be shown in UI, it will be incomplete, because there were no upstream tables emited (parsed from SQL query).
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
Imagine we have an unsupported (by Tableau) Custom SQL query like this:
id = c00a497c-2d83-4fd7-b259-35eb54f4d97d
It will parse SQL query and infer that the Custom SQL id = c00a497c-2d83-4fd7-b259-35eb54f4d97d is referencing upstream table t1, and its columns col1, col2. It will save table linage and fine-grained linage information for the Custom SQL entity.
But it does not emit the parsed tables itself (doesnot matter if
ingest_tables_external
was enabled or not), for those who has no ability to pre-ingest the tables, the linage will not be shown in UI, it will be incomplete, because there were no upstream tables emited (parsed from SQL query).The fix is by the link:
#9838
The text was updated successfully, but these errors were encountered: