On 1-Aug-07, at 11:34 AM, Joe Attardi wrote:
On 8/1/07, Erick Erickson <[EMAIL PROTECTED]> wrote:
Use a SpanNearQuery with a slop of 0 and specify true for ordering.
What that will do is require that the segments you specify must
appear
in order with no gaps. You have to construct this your
I suspect you're going to have to deal with wildcards if you really want
this functionality.
Erick
On 8/1/07, Joe Attardi <[EMAIL PROTECTED]> wrote:
>
> On 8/1/07, Erick Erickson <[EMAIL PROTECTED]> wrote:
> >
> > Use a SpanNearQuery with a slop of 0 and specify true for ordering.
> > What that w
On 8/1/07, Erick Erickson <[EMAIL PROTECTED]> wrote:
>
> Use a SpanNearQuery with a slop of 0 and specify true for ordering.
> What that will do is require that the segments you specify must appear
> in order with no gaps. You have to construct this yourself since there's
> no support for SpanQueri
Think of a custom analyzer class rather than an custom query parser. The
QueryParser uses your analyzer, so it all just "comes along".
Here's the approach I'd try first, off the top of my head
Yes, break the IP and etc. up into octets and index them
tokenized.
Use a SpanNearQuery with a slop
Hi Erick,
First, consider using your own analyzer and/or breaking the IP addresses
> up by substituting ' ' for '.' upon input.
Do you mean breaking the IP up into one token for each segment, like ["192",
"168", "1", "100"] ?
> But on to your question. Please post what you mean by
> "a large n
First, consider using your own analyzer and/or breaking the IP addresses
up by substituting ' ' for '.' upon input. Otherwise, you'll have endless
issues as time passes..
But on to your question. Please post what you mean by
"a large number". 10,000? 1,000,000,000? we have no clue
from your po
