[
https://issues.apache.org/jira/browse/SOLR-10928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated SOLR-10928:
----------------------------------
Labels: pull-request-available (was: )
> Support elevate.q in QueryElevationComponent
> --------------------------------------------
>
> Key: SOLR-10928
> URL: https://issues.apache.org/jira/browse/SOLR-10928
> Project: Solr
> Issue Type: Improvement
> Components: SearchComponents - other
> Reporter: jefferyyuan
> Priority: Critical
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> QueryElevationComponent uses the query in parameter to match the elevate.xml.
> "query text" from elevate.xml
> : has to match the query (q=...). So in this case, elevation works only for
> : http://localhost:8080/solr/elevate?q=brain, but not for
> : http://localhost:8080/solr/elevate?q=indexingabstract:brain type of
> queries.
> But sometimes, the query is more complex, we may use some nested query or
> complexphrase.
> it would also be fairly easy to make QEC support an "elevate.q" param
> similar to how there is a "spellcheck.q" param and a "hl.q" param to let the
> client specify an alternate, simplified, string for the feature to use.
> Conten copied from:
> http://lucene.472066.n3.nabble.com/Problems-with-elevation-component-configuration-td3993204.html
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
