Score details - #252
Conversation
2d7f6ab to
18e6e01
Compare
Co-authored-by: Maria Craig <marycraig90@gmail.com>
3906: Add "scoring.*" analytics to multi search route r=Kerollmops a=dureuill # Pull Request ## Related issue Fixes meilisearch/specifications#252 (comment) by implementing (3): multi search now returns the "score.show_ranking_rule" and "score.show_ranking_rule_details" analytics. Co-authored-by: Louis Dureuil <louis@meilisearch.com>
| | vector_store | Whether the [vector store](./0193-experimental-features.md#vector-store) feature is enabled. | `true` | `Experimental features Updated` | | ||
| | score_details | Whether the [score details](./0193-experimental-features.md#score-details) feature is enabled. | `true` | `Experimental features Updated` | | ||
| | scoring.show_ranking_score | Was `showRankingScore` used in the aggregated event? If yes, `true`, otherwise `false` | `false` | `Documents Searched POST`, `Documents Searched GET`, `Documents Searched by Multi-Search POST` | | ||
| | scoring.show_ranking_score_details | Was `showRankingScoreDetails` used in the aggregated event? If yes, `true`, otherwise `false` | `false` | `Documents Searched POST`, `Documents Searched GET`, `Documents Searched GET` | |
There was a problem hiding this comment.
| | scoring.show_ranking_score_details | Was `showRankingScoreDetails` used in the aggregated event? If yes, `true`, otherwise `false` | `false` | `Documents Searched POST`, `Documents Searched GET`, `Documents Searched GET` | | |
| | scoring.show_ranking_score_details | Was `showRankingScoreDetails` used in the aggregated event? If yes, `true`, otherwise `false` | `false` | `Documents Searched POST`, `Documents Searched GET`, `Documents Searched by Multi-Search POST` | |
🥅
| The score is given by the following formula, assuming `n` ranking rules denoted from `0` to `n-1`: | ||
|
|
||
| ``` | ||
| score = sum(i in 0..(n-1), (rank_i - 1) / product(j in 0..=i, max_rank_j)) + (rank_(n-1) / product(i in 0..n, max_rank_i)) |
| }, | ||
| "attribute": { | ||
| "order": 3, | ||
| "attributes_ranking_order": 0.8333333333333334, |
There was a problem hiding this comment.
Should it be written attributesRankingOrder to follow the camelCase field naming convention ?
There was a problem hiding this comment.
Yea Louis was onto me today about this. It looks like the implementation is outputting it with underscores rather than camelCase so will need a change there first (and then an update here and in the blog post to make sure they are the same). I'll create an issue on the project as a start point.
There was a problem hiding this comment.
Issue created here: meilisearch/meilisearch#3941
There was a problem hiding this comment.
Heya!
Here is the PR on Meilisearch fixing it https://github.com/meilisearch/meilisearch/pull/3949/files, however, there is a difference in the name chosen on Meilisearch side and in the spec:
attributeRankingOrderScore vs attributesRankingOrder and queryWordDistanceScore and attributesQueryWordOrder, which names should be chosen?
There was a problem hiding this comment.
Hey many 👋👶
attributeRankingOrderScore and queryWordDistanceScore
Relevant discussion (internal link)
| "attribute": { | ||
| "order": 3, | ||
| "attributes_ranking_order": 0.8333333333333334, | ||
| "attributes_query_word_order": 1, |
* Fix various typos * Fix wrongly tagged routes in open api * Telemetry policy * Add new error and api keys actions * Add experimental features and experimental feature API specs * Update open API * Score details (#252) * ranking score spec * search API changes * telemetry policies score * open api * Fix typos in spec Co-authored-by: Maria Craig <marycraig90@gmail.com> * Add multi search telemetry --------- Co-authored-by: Maria Craig <marycraig90@gmail.com> --------- Co-authored-by: Maria Craig <marycraig90@gmail.com>
| properties: | ||
| order: | ||
| $ref: '#/components/schemas/order' | ||
| attribute_ranking_order_score: |
There was a problem hiding this comment.
@dureuill @brunoocasali this attribute should be attributeRankingOrderScore ?
also query_word_distance_score => queryWordDistanceScore

🤖 API Diff Put the link of the GitHub comment generated by bump.sh if generated; Apply the
OpenApilabelSummary
Specify the ranking score and ranking score details.
Specification for meilisearch/meilisearch#3771
Changes
Out Of Scope
N/A
Attention To Reviewers
experimental_featuresbranch rather than therelease-v1.3.0branch. When merging, make sure to merge Experimental features #250 before this PR.Misc
OpenApilabel)Telemetrylabel)