[ https://issues.apache.org/jira/browse/SOLR-5973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995254#comment-13995254 ]
Otis Gospodnetic commented on SOLR-5973: ---------------------------------------- [~joel.bernstein] how does this play with SOLR-1680? I suspect it doesn't at all, right? Do you think SOLR-1680 has any merit or should it be Won't Fix-ed? > Pluggable Ranking Collectors > ---------------------------- > > 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 > > > 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. > A new "rq" http parameter was added to support specifying a rank query using > a custom QParserPlugin. > Sample syntax: > {code} > q=*:*&wt=json&indent=true&rq={!myranker} > {code} > In the sample above the param: {code}rq={!myranker}{code} points to a > QParserPlugin that returns a Query that extends RankQuery. -- 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