Hi Greg,
On Thu, May 19, 2011 at 12:26 PM, Gregory Tarr wrote:
> We let our users decide whether they want to force the order or not, so
> in effect they pass in "inOrder".
>
> I would have to detect a repeated term and change the parameter as a
> result of that in order to workround this - I'd r
riginal Message-
From: Doron Cohen [mailto:cdor...@gmail.com]
Sent: 19 May 2011 10:22
To: java-user@lucene.apache.org
Subject: Re: SpanNearQuery - inOrder parameter
Hi Greg,
I created http://issues.apache.org/jira/browse/LUCENE-3120 for this
problem, and attached there a more general test th
>
> Greg
>
> -Original Message-
> From: Gregory Tarr
> Sent: 13 May 2011 15:46
> To: 'java-user@lucene.apache.org'
> Subject: RE: SpanNearQuery - inOrder parameter
>
> Chris, and others
>
> Thanks for your reply. In effect what you are saying is t
Anyone else able to reply to this?
Thanks
Greg
-Original Message-
From: Gregory Tarr
Sent: 13 May 2011 15:46
To: 'java-user@lucene.apache.org'
Subject: RE: SpanNearQuery - inOrder parameter
Chris, and others
Thanks for your reply. In effect what you are saying is that
Spa
etter [mailto:hossman_luc...@fucit.org]
Sent: 11 May 2011 00:32
To: java-user@lucene.apache.org
Subject: RE: SpanNearQuery - inOrder parameter
: I attach a junit test which shows strange behaviour of the inOrder
: parameter on the SpanNearQuery constructor, using Lucene 2.9.4.
:
: My understanding of
: I attach a junit test which shows strange behaviour of the inOrder
: parameter on the SpanNearQuery constructor, using Lucene 2.9.4.
:
: My understanding of this parameter is that true forces the order and
: false doesn't care about the order.
:
: Using true always works. However using false
gt;
> Thanks
>
> Greg
>
> -Original Message-
> From: Gregory Tarr [mailto:gregory.t...@detica.com]
> Sent: 09 May 2011 12:33
> To: java-user@lucene.apache.org
> Subject: RE: SpanNearQuery - inOrder parameter
>
> Attachment didn't work - test below:
>
Anyone able to help me with the problem below?
Thanks
Greg
-Original Message-
From: Gregory Tarr [mailto:gregory.t...@detica.com]
Sent: 09 May 2011 12:33
To: java-user@lucene.apache.org
Subject: RE: SpanNearQuery - inOrder parameter
Attachment didn't work - test below:
i
setting inOrder = false
q = new SpanNearQuery(clauses, 0, false);
searcher.search(q, collector);
// This assert fails - 3 docs are returned. Expecting only DOC2
Assert.assertEquals("Check 1 result", 1, collector.getTotalHits());
}
}
____
From: Gregory
I attach a junit test which shows strange behaviour of the inOrder
parameter on the SpanNearQuery constructor, using Lucene 2.9.4.
My understanding of this parameter is that true forces the order and
false doesn't care about the order.
Using true always works. However using false works fine when
10 matches
Mail list logo
