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

Column lineage query returning null for namespace and name #2875

Closed
mattwparas opened this issue Aug 12, 2024 · 3 comments · Fixed by #2881
Closed

Column lineage query returning null for namespace and name #2875

mattwparas opened this issue Aug 12, 2024 · 3 comments · Fixed by #2881

Comments

@mattwparas
Copy link
Contributor

It looks like with this change #2821, the column lineage query returns null values, which causes the get dataset endpoint to 500 since namespace and name are marked as non null. I've tested with the old query and it returns the column lineage properly. I have not yet investigated as to why

@davidsharp7
Copy link
Member

Have you got some examples we could look at?

@mattwparas
Copy link
Contributor Author

mattwparas commented Aug 15, 2024

Yeah, I can paste some examples - its a bit difficult since we've got quite a bit of data so I'll try to distill it down to something manageable

@sophiely
Copy link
Contributor

Hi all !

I face the same issue here.
I feel like it's because the namespace and name are provided thanks to the datasets_view but this view only contains the latest version of a dataset.
Sometimes the column lineage is created by an ulterior version so this version won't be find if the datasets_view, I fix the query so as we read in the datasets_version table and not the dataset_views.
Let me know what you think :)

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

Successfully merging a pull request may close this issue.

3 participants