Pilot error... I had a cut & paste error and was indexing "C D" as the
document I said I was indexing as "D". Sorry about that.
Thanks, david.
On 5/16/07, Doron Cohen <[EMAIL PROTECTED]> wrote:
> Query Parsed As Matches Matches
> - -
> Query Parsed As Matches Matches
> - - ---
> NOT B -body:B 2, 4
> *:* NOT B MatchAllDocsQuery -body:B 2, 4 2, 4, 5
> *.* AND NOT B +MatchAllDocsQuery -body:B 2, 4 2, 4, 5
: 5 B
: Expected Actual
: Query Parsed As Matches Matches
: - - ---
: NOT B -body:B 2, 4
: *:* NOT B MatchAllDocsQuery -body:B 2, 4
I see my tables didn't come through so well. Here's (I hope) a plain
text version:
I understand that it would be best to have a UI that mapped lists of
terms to MUST, MUST_NOT and SHOULD, but I'm currently constrained to
using the QueryParser with boolean operators.
Given that, I was thinking th
I understand that it would be best to have a UI that mapped lists of terms
to MUST, MUST_NOT and SHOULD, but I'm currently constrained to using the
QueryParser with boolean operators.
Given that, I was thinking that the addition of "*:*" (in 2.1) to represent
MatchAllDocsQuery might help solve:
: When I enter the query: "Table AND NOT Chair" I get one hit, doc3
: When I enter the query: "Table AND (NOT Chair)" I get 0 hits.
:
: I had thought that both queries would return the same results. Is this a
: bug, or, am I not understanding the query language correctly?
it's a confusing eccen
