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

GEN-1434: Improvement : Show displayName for database and databaseSchema in explore tree #17876

Merged
merged 9 commits into from
Sep 26, 2024

Conversation

sonika-shah
Copy link
Contributor

@sonika-shah sonika-shah commented Sep 17, 2024

Describe your changes:

Show displayName for database and databaseSchema in explore tree

Backend changes-

  • Added new aggregation database.displayName and databaseSchema.displayName.keyword on dataAsset
  • Added displayName field to the database and databaseSchema in all relevant Elasticsearch indices
Screen.Recording.2024-09-26.at.11.53.25.AM.mov

Type of change:

  • Bug fix
  • Improvement
  • New feature
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation

Checklist:

  • I have read the CONTRIBUTING document.
  • My PR title is Fixes <issue-number>: <short explanation>
  • I have commented on my code, particularly in hard-to-understand areas.
  • For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

Copy link
Contributor

github-actions bot commented Sep 17, 2024

Jest test Coverage

UI tests summary

Lines Statements Branches Functions
Coverage: 64%
64.38% (37427/58130) 41.1% (14873/36185) 43.14% (4515/10466)

sushi30
sushi30 previously approved these changes Sep 19, 2024
@karanh37 karanh37 changed the title Improvement : Show displayName for database and databaseSchema in explore tree GEN-1434: Improvement : Show displayName for database and databaseSchema in explore tree Sep 19, 2024
Copy link

super.entityRelationshipReindex(original, updated);

// Update search indexes of assets and entity on database displayName change
if (!Objects.equals(original.getDisplayName(), updated.getDisplayName())) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need to do this explicitly, will the updateEntity() in search not take care of this ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

updateEntity() currents only updates the inherited and propagated fields in children and not other fields of the parent entity

super.entityRelationshipReindex(original, updated);

// Update search indexes of assets and entity on databaseSchema displayName change
if (!Objects.equals(original.getDisplayName(), updated.getDisplayName())) {
Copy link
Contributor

Choose a reason for hiding this comment

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

We are reindexing the whole entity on just displayNameChange, should we just update the disaplayName?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

this improvement will be handled in a different pr, will link the pr once it is ready

Copy link

sonarcloud bot commented Sep 26, 2024

Copy link

sonarcloud bot commented Sep 26, 2024

@karanh37 karanh37 merged commit a99fbb2 into main Sep 26, 2024
26 of 27 checks passed
@karanh37 karanh37 deleted the show-display-name-explore-tree branch September 26, 2024 10:48
karanh37 pushed a commit that referenced this pull request Sep 27, 2024
…ema in explore tree (#17876)

* Show displayName for database and databaseSchema in explore tree

* use display name for database and schema

* add playwright

* resync indexes of dataAssets based on database & databaseSchema displayName change

---------

Co-authored-by: karanh37 <karanh37@gmail.com>
Co-authored-by: Karan Hotchandani <33024356+karanh37@users.noreply.github.com>
(cherry picked from commit a99fbb2)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend safe to test Add this label to run secure Github workflows on PRs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants