[
https://issues.apache.org/jira/browse/SOLR-9531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Benedetti updated SOLR-9531:
---------------------------------------
Description:
Currently the queryElevation component will elevate specific documents matching
the Id provided in input.
This is generally correct as we need to be sure the ID we boost is unique.
This can be potentially problematic when used with the field collapsing.
Specifically after we collapsed on fieldA, the collapsed results will have a
unique value on fieldA.
This issue is to allow the flexibility, when necessary to elevate documents
based on a different unique field instead of the primary key.
e.g.
In the index we store products by different suppliers.
Each document has:
the unique Id : <id>
the Id of the product : <productId>
After collapsing on productId, productId will become unique and a good
candidate for the queryElevation component.
- This issue will implement an additional request parameter for the
queryElevation component : idField
The code will then be changed to be parametric.
I will take a look to the code, not sure if it is possible.
User responsibility will be to provide idField which make sense.
was:
Currently the queryElevation component will elevate specific documents matching
the Id provided in input.
This is generally correct as we need to be sure the ID we boost is unique.
This can be potentially problematic when used with the field collapsing.
Specifically after we collapsed on fieldA, the collapsed results will have a
unique value on fieldA.
This issue is to allow the flexibility, when necessary to elevate documents
based on a different unique field instead of the primary key.
e.g.
In the index we store products by different suppliers.
Each document has:
the unique Id : <id>
the Id of the product : <productId>
After collapsing on productId, productId will become unique and a good
candidate for the queryElevation component.
- This issue will implement an additional request parameter for the
queryElevation component : idField
The code will then be changed to be parametric ( quite a simple change) .
User responsibility will be to provide idField which make sense.
> QueryElevation component parametric field as doc IdField
> --------------------------------------------------------
>
> Key: SOLR-9531
> URL: https://issues.apache.org/jira/browse/SOLR-9531
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 6.2
> Reporter: Alessandro Benedetti
> Labels: component, elevation, query
>
> Currently the queryElevation component will elevate specific documents
> matching the Id provided in input.
> This is generally correct as we need to be sure the ID we boost is unique.
> This can be potentially problematic when used with the field collapsing.
> Specifically after we collapsed on fieldA, the collapsed results will have a
> unique value on fieldA.
> This issue is to allow the flexibility, when necessary to elevate documents
> based on a different unique field instead of the primary key.
> e.g.
> In the index we store products by different suppliers.
> Each document has:
> the unique Id : <id>
> the Id of the product : <productId>
> After collapsing on productId, productId will become unique and a good
> candidate for the queryElevation component.
> - This issue will implement an additional request parameter for the
> queryElevation component : idField
> The code will then be changed to be parametric.
> I will take a look to the code, not sure if it is possible.
> User responsibility will be to provide idField which make sense.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
