[
https://issues.apache.org/jira/browse/SOLR-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13842314#comment-13842314
]
Joel Bernstein commented on SOLR-5541:
--------------------------------------
Wondering if having two separate elevation components would be confusing?
Looking through the code it looks like the XML config loading happens on demand
so it wouldn't get triggered by accident. Also the component needs to be
switched on so it seems like it would be safe in the default list.
> 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]
