[
https://issues.apache.org/jira/browse/SOLR-16913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Chopin updated SOLR-16913:
------------------------------
Description: Jira bugged out and posted this twice, it's a copy of
SOLR-16912 (was: When the `match=subset` option is given inside elevate.xml,
results are not elevated even if their search terms contained within the user's
(longer) query. In other words, elevation works the same way irrespective of
whether the `match=subset` option is given or not.
_Steps to reproduce:_
1. Load the techproducts example
2. Set the techproducts example's elevate.xml to:
{code:java}
<elevate>
<query text="foo bill" match="subset">
<doc id="IW-02" />
</query>
</elevate>{code}
3. The folllowing query should trigger "IW-02" to appear in the results, but it
does not:
[http://localhost:8983/solr/techproducts/elevate?q=foo%20bill%20bar|http://localhost:8983/solr/techproducts/elevate?q=foo%20bill]
However the elevation can be seen to be working with the query:
[http://localhost:8983/solr/techproducts/elevate?q=foo%20bill])
> Query Elevation does not work with match=subset option
> ------------------------------------------------------
>
> Key: SOLR-16913
> URL: https://issues.apache.org/jira/browse/SOLR-16913
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 8.3, 8.11.2, 9.3
> Reporter: Tom Chopin
> Priority: Major
>
> Jira bugged out and posted this twice, it's a copy of SOLR-16912
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
