-
Notifications
You must be signed in to change notification settings - Fork 3k
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
refactor(ingest/biz-glossary): simplify business glossary source #7912
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can give a deeper review if necessary but I really have no clue what I'm reading. Someone more familiar with this source should probably review instead
metadata-ingestion/src/datahub/ingestion/source/metadata/business_glossary.py
Outdated
Show resolved
Hide resolved
metadata-ingestion/src/datahub/ingestion/source/confluent_schema_registry.py
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One suggestion but LGTM
materialize_all_node_urns(glossary_config, self.config.enable_auto_id) | ||
path_vs_id = populate_path_vs_id(glossary_config) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we do these two together? The recursion looks the same and it seems like after the urns are calculated we can just alter path_vs_id
after we define the urn
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I use them separately here https://github.com/acryldata/business-glossary-sync-action/blob/main/glossary-sync.py#L473, which is why I structured it this way
Checklist