For your own implementation you'll need to implement the following methods:
public Query rewrite(IndexReader reader) throws IOException public void extractTerms(Set<Term> terms) You can review the 4.10.3 version of the ReRankQParserPlugin to see how it implements these methods. Joel Bernstein http://joelsolr.blogspot.com/ On Wed, Apr 22, 2015 at 7:33 PM, Joel Bernstein <joels...@gmail.com> wrote: > Just confirmed that wildcard queries work with Re-Ranking following > SOLR-6323. > > Joel Bernstein > http://joelsolr.blogspot.com/ > > On Wed, Apr 22, 2015 at 7:26 PM, Joel Bernstein <joels...@gmail.com> > wrote: > >> This should be resolved in >> https://issues.apache.org/jira/browse/SOLR-6323. >> >> Solr 4.10.3 >> >> Joel Bernstein >> http://joelsolr.blogspot.com/ >> >> On Wed, Apr 15, 2015 at 6:23 PM, Ryan Josal <rjo...@gmail.com> wrote: >> >>> Using edismax, supplying a rq= param, like {!rerank ...} is causing an >>> UnsupportedOperationException because the Query doesn't implement >>> createWeight. This is for WildcardQuery in particular. From some >>> preliminary debugging it looks like without rq, somehow the qf Queries >>> might turn into ConstantScore instead of WildcardQuery. I don't think >>> this >>> is related to the RankQuery implementation as my own subclass has the >>> same >>> issue. Anyway the effect is that all q's containing ? or * return http >>> 500 >>> because I always have rq on. Can anyone confirm if this is a bug? I >>> will >>> log it in Jira if so. >>> >>> Also, does anyone know how I can work around it? Specifically, can I >>> disable edismax from making WildcardQueries? >>> >>> Ryan >>> >> >> >
