[
https://issues.apache.org/jira/browse/SOLR-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-5541:
---------------------------------
Attachment: SOLR-5541.patch
Added a new patch. In the initial patches I was piggy backing a convenience
method that was used by the test cases to manually set the elevateIds and
excludeIds. This method was using an in memory cache would hold all the queries
that were in the elevation xml file.
This approach would cause a memory leak when doing large scale query elavation,
which this patch is designed to support.
This patch stops piggy backing that convenience method and adds a new method
that doesn't interact with the elevation cache.
> 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, SOLR-5541.patch, SOLR-5541.patch,
> 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.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
