In a way that certainly needs more testing (haven't had the time), but here
is the gist:
I modified the SpanNotQuery to allow a certain number of span crossings--
making it something of a WithinSpanQuery. So instead of just being able to
say find "something" and "something else" and don't let it
Mark,
you wrote:
> > On another note...http://famestalker.com
> >
...
>
> http://famestalker.com/devwiki/
Could you explain how "Paragraph/Sentence Proximity Searching"
is implemented in Qsol?
Regards,
Paul Elschot
-
To unsub
I realize my statement of dread may be news to some; here are my references.
QueryParser not handling queries containing AND and OR
http://issues.apache.org/jira/browse/LUCENE-167
Query Parser flags clauses with explicit OR as required when followed by
explicit AND
http://issues.apache.org/jir
On another note...http://famestalker.com
/devwik/ will be done soon...I only
The url gives a not found 404 error here.
Due to a typo on my part:
http://famestalker.com/devwiki/
On 10/13/06, Paul Elschot <[EMAIL PROTECTED]> wrote:
On Friday 13 October 2006 01:55, Mark Miller wrote:
> The
On Friday 13 October 2006 01:55, Mark Miller wrote:
> There is also the Surround Query Parser in contrib by the way...I would bet
> that Paul will tell you that it does not have these issues. I can't wait to
Indeed.
> see the replies on this one...I didn't realize that the QueryParser had
> these
On Oct 12, 2006, at 7:11 PM, Renaud Waldura wrote:
I'm developing an application used by scientists -- people who have
a pretty good idea of what logic is -- and they were shocked to
find out that neither of these queries return the same results:
1- banana AND apple OR orange
2- banana AND
Renaud Waldura wrote:
While we are also developing a query-building UI, users must be able to
enter text queries as well. What do other folks do? I mean, this is
pretty bad. I can hardly go back to my scientists and tell them Lucene
is unable to handle 2 boolean operators, that they should pare
There is also the Surround Query Parser in contrib by the way...I would bet
that Paul will tell you that it does not have these issues. I can't wait to
see the replies on this one...I didn't realize that the QueryParser had
these problems and am a bit skeptical...unfortunately I am away from home
