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

Data lineage between different database services is not showing #11

Open
abhilashaam opened this issue Feb 29, 2024 · 3 comments
Open
Assignees
Labels

Comments

@abhilashaam
Copy link

We have openmetadata setup on AKS clsuter using helm chart. we have connected databricks and azure sql database services. when we create table on databricks using a table from azure sql, the data lineage should be azure_sql_table --> databricks_table, but this lineage is not coming, we can see lineage between tables on databricks, like databricls_table1 --> databricks_table2. we tried creating tables with openmetadata-spark-agent as well as openmetadata-spark-agent-1.0-beta, nothing is giving expected result.

@abhilashaam
Copy link
Author

Hi team, Any update on this issue?

@ShaileshParmar11 ShaileshParmar11 moved this to Lineage - Mayur, Karan, Himank, Suresh in Release 1.4.0 Mar 6, 2024
@ulixius9 ulixius9 removed this from Release 1.4.0 Apr 22, 2024
@Madhur-Jatiya
Copy link

Is lineage btwn 2 different tables in the single database is possible?

@ulixius9
Copy link
Member

@Madhur-Jatiya yes that is possible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants