Displaying 4 results from an estimated 4 matches for "boolean_any_case".
2018 Sep 30
3
xapian parser bug?
...OT (((Kspam OR Kdeleted) OR Kmuted) OR Kbad-address)))
If it was on the right-hand side of AND_NOT it would be eliminated
(because the right-hand side doesn't contribute any weight anyway).
FWIW, I also couldn't reproduce this (I tried with quest and 1.4.7):
$ quest -psubject:S -fdefault,boolean_any_case 'subject:"and"'
Parsed Query: Query(Sand at 1)
Cheers,
Olly
2011 Sep 30
1
Slow phrase performance
...ms. I am not limiting the number of matches -- I
want all of them. But even on small sets like "kansas state" with
just 334 results, it's taking a long time.
The following are set:
$qp->set_default_op(OP_AND);
$qp->set_stemming_strategy(STEM_NONE);
Flags enabled: BOOLEAN,BOOLEAN_ANY_CASE,WILDCARD,PHRASE
------------------------------
I have been unable to find reports of other people experiencing the
same problem with poor phrase performance, so I am hoping it's simply
something that I'm doing wrong or ineffectively. Any help would be
appreciated.
Thanks!
2018 Sep 30
0
xapian parser bug?
Olly Betts <olly at survex.com> writes:
>
> FWIW, I also couldn't reproduce this (I tried with quest and 1.4.7):
>
> $ quest -psubject:S -fdefault,boolean_any_case 'subject:"and"'
> Parsed Query: Query(Sand at 1)
>
Ah, OK, it must have something to do with the way that notmuch is using
field processors. And I see now that the following code (from
lib/regexp-fields.cc) is probably related (at least it explains
subject:" not"...
2018 Sep 29
2
xapian parser bug?
Today we noticed that keywords can't be searched as prefixed terms. Or
that's what it looks like anyway. I tested and, or, and not.
╰─% NOTMUCH_DEBUG_QUERY=y notmuch search 'subject:"and"'
Query string is:
subject:"and"
notmuch search: A Xapian exception occurred
A Xapian exception occurred parsing query: Syntax: <expression> AND <expression>
Query