Brian Goetz <[EMAIL PROTECTED]> writes:
> >doc.add(Field.Text("path", "d=100&a=102"));
>
> I have, finally, fixed the query parser to define query terms by
> exclusion instead of inclusion. The terms above, as well as the many
> other posted examples, should now work.
Wow, you fixed it just a few days after I mentioned it (or is is an
old issue?). Anyway, after having tested Lucene (and the
lucene-[dev|user] mailing lists) I am prepared to enter the Church
of Lucene community, and exit the swish-e swamp. (Ok, it's not a fair
contest, since I perform indexing and searching from a Java
program. But still.)
/Stefan B
>
> A side-effect of this is that special tokens, like && for AND, and ||
> for OR, must be separated from the query terms by spaces: if you want
> a && b, you have to say a && b, not a&&b. I don't think this should
> be a problem.
>
> Next up: NEAR. Everyone wants it, but we're looking for a decent
> syntax, and many of the good punctuation characters have already been
> snapped up (like brackets and braces for range queries.)
>
> We could use
> a NEAR b
> or
> a WITHIN N OF b
> but these both have the problem that they don't generalize well to
> phrases with more than two terms.
>
> Or we could have a (yet another) modifier on the quoted phrase query
> to set the slop --
>
> "Mickey Minnie"(5)
> or
> "Mickey Minnie" SLOP(5)
>
> Lots of possibilities exist, but so far they're all pretty
> yucky. Suggestions?
>
>
>
> --
> Brian Goetz
> Quiotix Corporation
> [EMAIL PROTECTED] Tel: 650-843-1300 Fax: 650-324-8032
>
> http://www.quiotix.com
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
