Lucene paid development for "SpanAndQuery" / "SpanAllNearQuery" support

Hi all, The company I work for is interested in the implementation of this ticket: https://issues.apache.org/jira/browse/LUCENE-3371 (Support for a "SpanAndQuery" / "SpanAllNearQuery") and is willing to pay for it. If you believe you have the know-how on implementing this and are interested, plea

Re: SortingMergePolicy moved to solr ?

Thank you, Michael. This is a great change, and I really appreciate Lucene dev team made it happen. On Wednesday, September 14, 2016, Michael McCandless < luc...@mikemccandless.com> wrote: > It's rather the opposite: index sorting has been made more "first > class" by being moved to Lucene's core

Re: SortingMergePolicy moved to solr ?

It's rather the opposite: index sorting has been made more "first class" by being moved to Lucene's core out of Lucene's misc module. Instead of setting SortingMergePolicy, which is weird, you now call IndexWriterConfig.setIndexSort. SortingMergePolicy was only moved to solr for back-compat requi

Re: How to get all matched terms in a PrefixQuery

Also please realize that PrefixQuery, at default settings, will sometimes (often, depending on how you use it) bypass BooleanQuery and do the "term at a time" rewrite, which foils your effort. You could force PrefixQuery to always use BooleanQuery (setRewriteMethod), but this can cause horrific pe

Re: How to get all matched terms in a PrefixQuery

Rajnish, Thought you should be aware of LUCENE-6229 which discusses the possibility of removing the Scorer.getChildren API. --Terry On Tue, Sep 13, 2016 at 11:10 PM, Rajnish kamboj wrote: > Thanks Mike > > I would rather go with first approa

Re: "Suggester was not built" exception in Solr

You have to build suggesters, see the "suggest.build" parameter here: https://cwiki.apache.org/confluence/display/solr/Suggester Best, Erick On Wed, Sep 14, 2016 at 4:06 AM, Harsha JSN wrote: > Hi, > > I am getting "Suggester was not built" exception in Solr while fetching > suggestions. > > Sug

SortingMergePolicy moved to solr ?

Before 6.2, it is in Lucene-misc, now I can only find it in solr. I understand it might have something to do with an issue I reported earlier that sortingmergepolicy cannot handle point field properly, but my expectation by then was to expect this would be addressed in a later version instead of be

"Suggester was not built" exception in Solr

Hi, I am getting "Suggester was not built" exception in Solr while fetching suggestions. Suggester configuration: my_suggester BlendedInfixLookupFactory DocumentDictionaryFactory suggest_text weight_field 5 text false