Search using Learning To Rankedit
The Learning To Rank feature is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but this feature is not subject to the support SLA of official GA features.
This feature was introduced in version 8.12.0 and is only available to certain subscription levels. For more information, see https://www.elastic.co/subscriptions.
Learning To Rank as a rescoreredit
Once your LTR model is trained and deployed in Elasticsearch, it can be used as a rescorer in the search API:
GET my-index/_search
{
"query": {
"multi_match": {
"fields": ["title", "content"],
"query": "the quick brown fox"
}
},
"rescore": {
"learning_to_rank": {
"model_id": "ltr-model",
"params": {
"query_text": "the quick brown fox"
}
},
"window_size": 100
}
}
|
First pass query providing documents to be rescored. |
|
|
The unique identifier of the trained model uploaded to Elasticsearch. |
|
|
Named parameters to be passed to the query templates used for feature. |
|
|
The number of documents that should be examined by the rescorer on each shard. |
Known limitationsedit
Rescore window sizeedit
Scores returned by LTR models are usually not comparable with the scores issued by the first pass query and can be lower than the non-rescored score. This can cause the non-rescored result document to be ranked higher than the rescored document. To prevent this, the window_size parameter is mandatory for LTR rescorers and should be greater than or equal to from + size.
Paginationedit
When exposing pagination to users, window_size should remain constant as each page is progressed by passing different from values. Changing the window_size can alter the top hits causing results to confusingly shift as the user steps through pages.
Negative scoresedit
Depending on how your model is trained, it’s possible that the model will return negative scores for documents. While negative scores are not allowed from first-stage retrieval and ranking, it is possible to use them in the LTR rescorer.
Compatibility with field collapsingedit
LTR rescorers are not compatible with the collapse feature.
Term statistics as featuresedit
We do not currently support term statistics as features, however future releases will introduce this capability.