Re: Positions in SpanFirst

2007-02-22 Thread Antony Bowesman
Chris Hostetter wrote: : So I don't see why using a SpanNear that respects order and a large : IncrementGap won't solve your problem.. Although it would return "odd" i think the use case he's worreid about is that he needs to be able to find matches just on the "start" of a persons name, ie.

Re: Positions in SpanFirst

2007-02-21 Thread Chris Hostetter
: So I don't see why using a SpanNear that respects order and a large : IncrementGap won't solve your problem.. Although it would return "odd" i think the use case he's worreid about is that he needs to be able to find matches just on the "start" of a persons name, ie... Email#1 To:

Re: Positions in SpanFirst

2007-02-21 Thread Erick Erickson
I really think you need to stop obsessing on SpanFirst . I suspect that this is leading you down an unrewarding path. So I don't see why using a SpanNear that respects order and a large IncrementGap won't solve your problem.. Although it would return "odd" matches. Let's say you indexed "firs

Re: Positions in SpanFirst

2007-02-21 Thread Antony Bowesman
Ahh, now it falls into place. Thanks Antony Chris Hostetter wrote: it's not called Analyzer.getPositionAfterGap .. it's Analyzer.getPositionIncrementGap .. it's the Position Increment used when there is a Gap -- so returning 0 means that no exra increment is used, and multiple values are treate

Re: Positions in SpanFirst

2007-02-21 Thread Chris Hostetter
: So, if you can add 1000, shouldn't setting 0 each time cause it to start at 0 : each time? The default Analyzer.getPositionIncrementGap always returns 0. it's not called Analyzer.getPositionAfterGap .. it's Analyzer.getPositionIncrementGap .. it's the Position Increment used when there is a Ga

Re: Positions in SpanFirst

2007-02-21 Thread Antony Bowesman
Hi Erick, What this does is allow you to put gaps between successive sets of terms indexed in the same field. For instance... doc.add("field", "some stuff"); doc.add("field", "bunch hooey"); doc.add("field", "what is this"); writer.add(doc); In this case, there would be the following positions,

Re: Positions in SpanFirst

2007-02-21 Thread Chris Hostetter
: so I thought that sounded good, but there does not seem to be a way to set it : and most of the Analyzers just seem to use the base Analyzer method which : returns 0, so I'm now confused as to what this actually does in practice. by default all the analyzers return 0, but you can subclass any a

Re: Positions in SpanFirst

2007-02-21 Thread Erick Erickson
See below.. On 2/21/07, Antony Bowesman <[EMAIL PROTECTED]> wrote: Hi Erick, > I'm not sure you can, since all the interfaces I use alter the increment > between successive terms, but I'll be the first to admit that there are > many > nooks and crannies that I don't know about... But I suspect

Re: Positions in SpanFirst

2007-02-21 Thread Antony Bowesman
Hi Erick, I'm not sure you can, since all the interfaces I use alter the increment between successive terms, but I'll be the first to admit that there are many nooks and crannies that I don't know about... But I suspect that a negative increment is not supported intentionally I read your

Re: Positions in SpanFirst

2007-02-21 Thread Erick Erickson
I'm not sure you can, since all the interfaces I use alter the increment between successive terms, but I'll be the first to admit that there are many nooks and crannies that I don't know about... But I suspect that a negative increment is not supported intentionally But I really doubt you wan

Positions in SpanFirst

2007-02-21 Thread Antony Bowesman
Hi, I have a field to which I add several bits of information, e.g. doc.add(new Field("x", "first bit")); doc.add(new Field("x", "second part")); doc.add(new Field("x", "third section")); I am using SpanFirstQuery to search them with something like: while... SpanTermQuery stquery = new SpanT