[
https://issues.apache.org/jira/browse/SOLR-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13842301#comment-13842301
]
Hoss Man commented on SOLR-5541:
--------------------------------
Joel: This smells like the kind of thing that could easily be it's own
Component (using a common base class with the existing QueryElevationComponent
containing code refactored out of QEC) .. and since this new type of elevation
wouldn't require any explicit XML configuration, it could concievably be be
wired into the default list of components in SearchHandler.
thoughts?
> Allow QueryElevationComponent to accept elevateIds and excludeIds as http
> parameters
> ------------------------------------------------------------------------------------
>
> Key: SOLR-5541
> URL: https://issues.apache.org/jira/browse/SOLR-5541
> Project: Solr
> Issue Type: Improvement
> Components: SearchComponents - other
> Affects Versions: 4.6
> Reporter: Joel Bernstein
> Assignee: Joel Bernstein
> Priority: Minor
> Fix For: 4.7
>
> Attachments: SOLR-5541.patch
>
>
> The QueryElevationComponent currently uses an xml file to map query strings
> to elevateIds and excludeIds.
> This ticket adds the ability to pass in elevateIds and excludeIds through two
> new http parameters "elevateIds" and "excludeIds".
> This will allow more sophisticated business logic to be used in selecting
> which ids to elevate/exclude.
> Proposed syntax:
> http://localhost:8983/solr/elevate?q=*:*&elevatedIds=3,4&excludeIds=6,8
> The elevateIds and excludeIds point to the unique document Id.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
