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

fix(ingest/csv-enricher): Adding extra check in csv enricher to ignore non-urn urns #8169

Merged
merged 2 commits into from
Jun 23, 2023

Conversation

treff7es
Copy link
Contributor

@treff7es treff7es commented Jun 5, 2023

Checklist

  • The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
  • Links to related issues (if applicable)
  • Tests for the changes have been added/updated (if applicable)
  • Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
  • For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@github-actions github-actions bot added the ingestion PR or Issue related to the ingestion of metadata label Jun 5, 2023
Copy link
Collaborator

@asikowitz asikowitz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I could see it being disorienting if you went to ingest a file and just didn't get some of the data, with no logging / messaging around the absences. Could you either making the glossary term / tag/ owner aspect creation more forgiving or adding messaging?

Comment on lines +549 to +551
GlossaryTermAssociationClass(term)
for term in term_urns
if term.startswith("urn:li:")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this just due to an ill-formatted file? Can we instead append url:li if it doesn't start with that, like we do elsewhere in make_data_platform_urn for example

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No that is not possible. People are using this for terms while their actual URNs are UUIDs.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Feel free to stamp this one then. I don't understand what's going on here

@anshbansal anshbansal merged commit 726ee0f into datahub-project:master Jun 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ingestion PR or Issue related to the ingestion of metadata
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants