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(patch-entity-registry): Remove exception for entities with key aspects. #5831

Merged
merged 7 commits into from
Sep 7, 2022

Conversation

pghazanfari
Copy link
Contributor

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

@shirshanka shirshanka added community-contribution PR or Issue raised by member(s) of DataHub Community platform PR-s that make changes to core parts of the platform labels Sep 6, 2022
@github-actions
Copy link

github-actions bot commented Sep 6, 2022

Unit Test Results (build & test)

517 tests  ±0   517 ✔️ ±0   9m 33s ⏱️ + 1m 20s
121 suites ±0       0 💤 ±0 
121 files   ±0       0 ±0 

Results for commit c0b3641. ± Comparison against base commit 08622f2.

♻️ This comment has been updated with latest results.

@pghazanfari
Copy link
Contributor Author

I thought I had the unit test passing locally, but it looks like I was mistaken. I added another commit that should fix the unit test.

@pghazanfari
Copy link
Contributor Author

pghazanfari commented Sep 6, 2022

@RyanHolstien Should I be merging in the latest changes whenever I can? Since I am a first time contributor the automated checks do not run unless triggered by someone, and they'll need to be run again when I merge in the latest changes. This seems like it would cause a lot of unnecessary overhead trying to time it right.

@RyanHolstien
Copy link
Collaborator

@RyanHolstien Should I be merging in the latest changes whenever I can? Since I am a first time contributor the automated checks do not run unless triggered by someone, and they'll need to be run again when I merge in the latest changes. This seems like it would cause a lot of unnecessary overhead trying to time it right.

No you don't have to repeatedly merge unless there are actual merge conflicts that prevent merging 🙂 just haven't had a chance to review yet. Will take a look through.

// aspectSpecs.add(getAspectSpec(entity.getKeyAspect(), entitySpecBuilder));
AspectSpec keyAspectSpec = buildAspectSpec(entity.getKeyAspect(), entitySpecBuilder);
log.info("Adding key aspect {} with spec {}", entity.getKeyAspect(), keyAspectSpec);
aspectSpecs.add(keyAspectSpec);;
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can you remove this second semi-colon? Otherwise lgtm

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good catch. I'll remove it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Assuming there are no other changes needed, would you be able to merge the change in? I don't have write access.

@RyanHolstien RyanHolstien merged commit 5a07745 into datahub-project:master Sep 7, 2022
@pghazanfari pghazanfari deleted the fix-patch-registry branch September 7, 2022 19:46
shirshanka pushed a commit to shirshanka/datahub that referenced this pull request Sep 8, 2022
…pects. (datahub-project#5831)

* fix(patch-entity-registry): Remove exception for entities with key aspects.

* test(patch-entity-registry): Fix failing unit test for entities with key aspect

* test(patch-entity-registry): Fix checkstyle for PatchEntityRegistryTest.java

* fix(patch-entity-registry): Remove duplicate semicolon.

Co-authored-by: Parham Ghazanfari <[email protected]>
shirshanka pushed a commit to shirshanka/datahub that referenced this pull request Sep 8, 2022
…pects. (datahub-project#5831)

* fix(patch-entity-registry): Remove exception for entities with key aspects.

* test(patch-entity-registry): Fix failing unit test for entities with key aspect

* test(patch-entity-registry): Fix checkstyle for PatchEntityRegistryTest.java

* fix(patch-entity-registry): Remove duplicate semicolon.

Co-authored-by: Parham Ghazanfari <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community-contribution PR or Issue raised by member(s) of DataHub Community platform PR-s that make changes to core parts of the platform
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants