[ 
https://issues.apache.org/jira/browse/SOLR-5973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997975#comment-13997975
 ] 

ASF subversion and git services commented on SOLR-5973:
-------------------------------------------------------

Commit 1594698 from [~joel.bernstein] in branch 'dev/trunk'
[ https://svn.apache.org/r1594698 ]

SOLR-5973: Pluggable Ranking Collectors and Merge Strategies

> Pluggable Ranking Collectors and Merge Strategies
> -------------------------------------------------
>
>                 Key: SOLR-5973
>                 URL: https://issues.apache.org/jira/browse/SOLR-5973
>             Project: Solr
>          Issue Type: New Feature
>          Components: search
>            Reporter: Joel Bernstein
>            Assignee: Joel Bernstein
>            Priority: Minor
>             Fix For: 4.9
>
>         Attachments: SOLR-5973.patch, SOLR-5973.patch, SOLR-5973.patch, 
> SOLR-5973.patch, SOLR-5973.patch, SOLR-5973.patch, SOLR-5973.patch, 
> SOLR-5973.patch, SOLR-5973.patch, SOLR-5973.patch, SOLR-5973.patch, 
> SOLR-5973.patch, SOLR-5973.patch, SOLR-5973.patch, SOLR-5973.patch
>
>
> This ticket introduces a new RankQuery and MergeStrategy to Solr. By 
> extending the RankQuery class, and implementing it's interface, you can 
> specify a custom ranking collector (TopDocsCollector) and distributed merge 
> strategy for a Solr query. 
> Sample syntax:
> {code}
> q={!customRank subquery=*:* param1=a param2=b}&wt=json&indent=true
> {code}
> In the sample above the param: {code}q={!customRank  subquery=*:* param1=a 
> param2=b}{code} points to a QParserPlugin that returns a Query that extends 
> RankQuery.  The RankQuery defines the custom ranking and merge strategy for 
> it's  subquery.
> The RankQuery impl will have to do several things:
> 1) Implement the RankQuery interface.
> 2) Wrap the subquery and proxy all calls to the Query interface to the 
> subquery. Using local params syntax the subquery can be any valid Solr query. 
> The custom QParserPlugin is responsible for parsing the subquery.
> 3)  Implement hashCode() and equals() so the queryResultCache works properly 
> with subquery and custom ranking algorithm. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to