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

feat(recomendations): Make top platforms account only for searchable entities #9240

Merged
merged 4 commits into from
Nov 15, 2023

Conversation

pedro93
Copy link
Collaborator

@pedro93 pedro93 commented Nov 14, 2023

This fixes a UI bug where if slack is configured or a custom platform for non-searchable entities is added, then those platforms are not counted towards platforms to be shown above the fold in the homepage.

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 devops PR or Issue related to DataHub backend & deployment label Nov 14, 2023
@@ -116,6 +117,11 @@ public List<RecommendationContent> getRecommendations(@Nonnull Urn userUrn,
.collect(Collectors.toList());
}

protected Filter buildAggregationFilter() {
Copy link
Collaborator

Choose a reason for hiding this comment

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

can we just have a method that liimits the entity indexes which are used for the query?

then the base class can just return a set of entity type names. what do you think?

Copy link
Collaborator Author

@pedro93 pedro93 Nov 14, 2023

Choose a reason for hiding this comment

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

Our Elastic SearchDAO is not prepared to received a set of entity names, it's either a specific one or null (which is all). It would be a greater lift to make multiple requests and 1 to each index and then merge all results or create a regex expression that matches for the set of entities we pass it.

Copy link
Collaborator

@RyanHolstien RyanHolstien left a comment

Choose a reason for hiding this comment

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

Looks good to me, don't think this should be a performance concern

@pedro93 pedro93 merged commit 6655918 into master Nov 15, 2023
37 checks passed
@pedro93 pedro93 deleted the ps-dynamic-top-platforms branch November 15, 2023 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops PR or Issue related to DataHub backend & deployment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants