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

Correct Search Behavior #124

Merged
merged 1 commit into from
Dec 2, 2022
Merged

Correct Search Behavior #124

merged 1 commit into from
Dec 2, 2022

Conversation

wjohnson
Copy link
Collaborator

@wjohnson wjohnson commented Dec 2, 2022

When Purview has a limit set to 1000, search scores are set to 1 and resulting in sub-optimal search result ordering. The custom connector generic is showing up first when other assets like sql tables and resource sets are showing up second.

This is solved by changing the default limit to 100 instead of 1000 (or any value less than 1000) and Microsoft Purview search scores are populating correctly.

When Purview has a limit set to 1000, search scores are set to 1 and resulting in sub-optimal
search result ordering. The custom connector generic is showing up first when other assets
like sql tables and resource sets are showing up second.

This is solved by changing the default limit to 100 instead of 1000 (or any value less than 1000)
and Microsoft Purview search scores are populating correctly.
@wjohnson wjohnson temporarily deployed to Integration December 2, 2022 05:28 Inactive
@wjohnson wjohnson merged commit 7b7f48c into main Dec 2, 2022
@wjohnson wjohnson deleted the feature/fixSearchPriority branch December 2, 2022 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants