Skip to content

Feature/9002 optimise reranking algorithm - #334

Merged
NekoLyn merged 9 commits into
mainfrom
feature/9002-optimise-reranking-algorithm
Aug 28, 2026
Merged

Feature/9002 optimise reranking algorithm#334
NekoLyn merged 9 commits into
mainfrom
feature/9002-optimise-reranking-algorithm

Conversation

@shaunahu

@shaunahu shaunahu commented Aug 25, 2026

Copy link
Copy Markdown
Contributor
  1. remove dataset_group from should clouse to sort option. So a matched dataset_group not contribute to the ES relevance score, but used for priority sorting. This aims to reduce the noises of current method, which gives matched dataset_group query a very high boost, and resulting in a matched organisation record even though have low relevance, it is still in the search result list.
image
  1. update the explain simplified response structure, to include sort options. So that easy to understand which field prioritised the record.
image
  1. use a shared createKeywordShouldClauses for both explain and search to build ES query

@shaunahu
shaunahu marked this pull request as ready for review August 27, 2026 07:13
@shaunahu
shaunahu requested a review from NekoLyn August 28, 2026 00:04

@NekoLyn NekoLyn left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

@NekoLyn
NekoLyn merged commit 506486e into main Aug 28, 2026
4 checks passed
@NekoLyn
NekoLyn deleted the feature/9002-optimise-reranking-algorithm branch August 28, 2026 01:57
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