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

Refresh of editableSchemaMetadata based on schemaMetadata #11642

Open
kartikey-visa opened this issue Oct 16, 2024 · 0 comments
Open

Refresh of editableSchemaMetadata based on schemaMetadata #11642

kartikey-visa opened this issue Oct 16, 2024 · 0 comments
Labels
bug Bug report

Comments

@kartikey-visa
Copy link
Contributor

Describe the bug
On ingestion when schemaMetadata of a dataset is refreshed like removal of columns, the same doesn't get reflected in editableSchemaMetadata and the linkings to the removed columns still exist in editableSchemaMetadata

To Reproduce
Steps to reproduce the behaviour:

  1. Attach glossary terms/business attributes to few columns of a dataset in datahub.
  2. Now delete those columns from source and re-ingest the dataset in datahub.
  3. Click on Related Entities tab of the glossary term which was attached to the now deleted column in dataset.
  4. Find or scroll down to that particular dataset it will still show up in Related Entities tab.
  5. Since the column to which glossary term was attached is now deleted, it should not show up in Related Entities, but it comes up in the list because the column along with its linkings (glossary terms etc.) still exists in editableSchemaMetadata

Expected behaviour
When the schemaMetadata of a dataset is updated (removal of columns), it should also update editableSchemaMetadata as part of its side effect.

Additional context
This problem is bound to occur in all the editable aspects of datahub.

@kartikey-visa kartikey-visa added the bug Bug report label Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug report
Projects
None yet
Development

No branches or pull requests

1 participant