(and Mark),
> >
> > Thank you for answering. Do you suppose "not really straightforward" means
> > "40 hours" or something like that? I'm just trying to get an idea of
> > whether what I'm attempting is worth the effort.
> >
> >
nt: Thu 3/4/2010 5:14 PM
To: java-dev@lucene.apache.org
Subject: Re: Request for clarification on unordered SpanNearQuery
All possible unordered matches with a given slop can be so many that
enumerating them all will be so slow that it is impractical for general use.
Note that I have not been very pre
>
>
> -Original Message-
> From: java-dev-return-47351-michael.j.goddard=saic@lucene.apache.org on
> behalf of Paul Elschot
> Sent: Thu 3/4/2010 11:51 AM
> To: java-dev@lucene.apache.org
> Subject: Re: Request for clarification on unordered SpanNearQuery
>
return-47351-michael.j.goddard=saic@lucene.apache.org on
behalf of Paul Elschot
Sent: Thu 3/4/2010 11:51 AM
To: java-dev@lucene.apache.org
Subject: Re: Request for clarification on unordered SpanNearQuery
Michael,
The test for the 4th range fails because the first matching subspans
(for t1 i
Michael,
The test for the 4th range fails because the first matching subspans
(for t1 in this case) is always the one that is first advanced, and the first
match at that point has a less slop (0) than the maximum allowed (1)
so one might actually try and advance another subspans first.
But that is
On 03/04/2010 11:34 AM, Goddard, Michael J. wrote:
// Question: why wouldn't this Span be found?
assertTrue("fourth range", spans.next());
assertEquals("fourth doc", 11, spans.doc());
assertEquals("fourth start", 2, spans.start());
assertEquals("fourth end", 6, spans.end());
Spa
I've been working on some highlighting changes involving Spans
(https://issues.apache.org/jira/browse/LUCENE-2287) and could use some help
understanding when overlapping Spans are valid. To illustrate, I added the
test below to the TestSpans class; this test fails because there is no fourth
ra
