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

chore(ingest/glue): cleanup deprecated underlying_platform config #7449

Merged
merged 2 commits into from
Feb 28, 2023

Conversation

hsheth2
Copy link
Collaborator

@hsheth2 hsheth2 commented Feb 27, 2023

This has been deprecated for 10 months now.

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

This has been deprecated for 10 months now.
@github-actions github-actions bot added the ingestion PR or Issue related to the ingestion of metadata label Feb 27, 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.

LGTM, one question for my own benefit

@@ -168,26 +164,17 @@ def s3_client(self):
@validator("glue_s3_lineage_direction")
def check_direction(cls, v: str) -> str:
if v.lower() not in ["upstream", "downstream"]:
raise ConfigurationError(
raise ValueError(
Copy link
Collaborator

Choose a reason for hiding this comment

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

How come you swap to ValueError here? Should all config validators raise ValueErrors?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

yes - with pydantic, you're supposed to raise ValueError or AssertionError

that way pydantic can (1) show if there are multiple validation issues and (2) shows the exact fields that failed validation alongside the errors

@hsheth2 hsheth2 merged commit 639bbcf into datahub-project:master Feb 28, 2023
@hsheth2 hsheth2 deleted the glue-config-dep branch February 28, 2023 18:41
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.

None yet

2 participants