Re: Single string automaton causes NPE on Terms.intersect( CompiledAutomaton, BytesRef term )

Hi José, Can you please open a Jira issue about this, and add a test case as a patch, if you can? I think it's bad you hit an NPE! Not sure how best to fix it, but we can iterate on the issue. Thanks! Mike McCandless http://blog.mikemccandless.com On Fri, Mar 25, 2016 at 7:11 PM, José

Re: Single string automaton causes NPE on Terms.intersect( CompiledAutomaton, BytesRef term )

Ok, digging a little more, I found that the problem mentioned above seems to be caused by FieldReader overriding the intersect( CompiledAutomaton, BytesRef )

Re: Subset Matching

There is no simple, direct way to do this "Boolean Reverse Query" in Lucene, but I suggest filing a Jira to request this as a feature improvement/new feature. -- Jack Krupansky On Fri, Mar 25, 2016 at 11:43 AM, Ahmet Arslan wrote: > Hi Otmar, > > For this

Re: Subset Matching

Hi Otmar, For this requirement, you need to create an additional field containing the number of words/terms in the field. For example. field : blue pill length = 2 query : if you take the blue pill length : 6 Please see my previous responses on the same topic:

Re: Subset Matching

Hi Otmar, Shouldn't Occur.SHOULD alone do what you ask? Documents that match all terms in the query would be scored higher than documents that match fewer than all terms. -sujit On Fri, Mar 25, 2016 at 2:20 AM, Otmar Caduff wrote: > Hi all > In Lucene, I know of the

Subset Matching

Hi all In Lucene, I know of the possibility of Occur.SHOULD, Occur.MUST and the “minimum should match” setting on the boolean query. Now, when querying, I want to - (1) match the documents which either contain all the terms of the query (Occur.MUST for all terms would do that) or, - (2) if all