Cameron Laird
2008-May-12 16:55 UTC
[Xapian-discuss] Symptom with twenty-five clause predicate
We embed Xapian in what amounts to a large Python application that has been
working
successfully for a couple of years. We recently came across a reproducible
instance
of a symptom whose pertinent traceback is
...
- __traceback_info__: ('+kind:"Files"
+(allow:"KarlAdmins" OR allow:"KarlStaff" OR
allow:"KarlSysAdmins" OR allow:"KarlTOSAccepted" OR
allow:"KarlTOSSent" OR allow:"NetworkNewsAdmins" OR
allow:"OSI-New York" OR allow:"Open Society Institute" OR
allow:"aboutkarl" OR allow:"cookingcommunity" OR
allow:"financialandadministrativeproceduresfaap" OR
allow:"freefood" OR
allow:"governinginternationalemergencies" OR
allow:"greenerosius" OR allow:"karladministration" OR
allow:"karlcoreteam" OR allow:"karlfeedbackcommunity" OR
allow:"karlpresentationatploneconference" OR
allow:"karlsuperusers" OR allow:"natscommunityofone" OR
allow:"oxfamdiscussion" OR allow:"thesoftersideofkarl" OR
allow:"zimbabwe") +US transparency and', None, None, True, None,
1, True)
Module lemur.xapian.sei, line 1761, in _makeQuery
Module xapian, line 1144, in parse_query
QueryParserError: Syntax: <expression> AND <expression>
...
Does this "ring any bells" with any of you? You're not
responsible for the faults
in our larger application, of course; I'm curious to know, though, whether
there
are any known limits to the scale of Xapian clause evaluation that might yield
this
sort of symptom.
I'll follow up with exact information on the versions of Xapian that exhibit
this
symptom.
Cameron Laird
2008-May-12 16:56 UTC
[Xapian-discuss] Symptom with twenty-five clause predicate
0.9.8 patched.
-----Original Message-----
From: Cameron Laird
Sent: Mon 5/12/2008 11:55 AM
To: xapian-discuss at lists.xapian.org
Subject: Symptom with twenty-five clause predicate
We embed Xapian in what amounts to a large Python application that has been
working
successfully for a couple of years. We recently came across a reproducible
instance
of a symptom whose pertinent traceback is
...
- __traceback_info__: ('+kind:"Files"
+(allow:"KarlAdmins" OR allow:"KarlStaff" OR
allow:"KarlSysAdmins" OR allow:"KarlTOSAccepted" OR
allow:"KarlTOSSent" OR allow:"NetworkNewsAdmins" OR
allow:"OSI-New York" OR allow:"Open Society Institute" OR
allow:"aboutkarl" OR allow:"cookingcommunity" OR
allow:"financialandadministrativeproceduresfaap" OR
allow:"freefood" OR
allow:"governinginternationalemergencies" OR
allow:"greenerosius" OR allow:"karladministration" OR
allow:"karlcoreteam" OR allow:"karlfeedbackcommunity" OR
allow:"karlpresentationatploneconference" OR
allow:"karlsuperusers" OR allow:"natscommunityofone" OR
allow:"oxfamdiscussion" OR allow:"thesoftersideofkarl" OR
allow:"zimbabwe") +US transparency and', None, None, True, None,
1, True)
Module lemur.xapian.sei, line 1761, in _makeQuery
Module xapian, line 1144, in parse_query
QueryParserError: Syntax: <expression> AND <expression>
...
Does this "ring any bells" with any of you? You're not
responsible for the faults
in our larger application, of course; I'm curious to know, though, whether
there
are any known limits to the scale of Xapian clause evaluation that might yield
this
sort of symptom.
I'll follow up with exact information on the versions of Xapian that exhibit
this
symptom.
James Aylett
2008-May-12 17:08 UTC
[Xapian-discuss] Symptom with twenty-five clause predicate
On Mon, May 12, 2008 at 11:55:03AM -0500, Cameron Laird wrote:> - __traceback_info__: ('+kind:"Files" +(allow:"KarlAdmins" OR allow:"KarlStaff" OR allow:"KarlSysAdmins" OR allow:"KarlTOSAccepted" OR allow:"KarlTOSSent" OR allow:"NetworkNewsAdmins" OR allow:"OSI-New York" OR allow:"Open Society Institute" OR allow:"aboutkarl" OR allow:"cookingcommunity" OR allow:"financialandadministrativeproceduresfaap" OR allow:"freefood" OR allow:"governinginternationalemergencies" OR allow:"greenerosius" OR allow:"karladministration" OR allow:"karlcoreteam" OR allow:"karlfeedbackcommunity" OR allow:"karlpresentationatploneconference" OR allow:"karlsuperusers" OR allow:"natscommunityofone" OR allow:"oxfamdiscussion" OR allow:"thesoftersideofkarl" OR allow:"zimbabwe") +US transparency and', None, None, True, None, 1, True) > Module lemur.xapian.sei, line 1761, in _makeQuery > Module xapian, line 1144, in parse_query > QueryParserError: Syntax: <expression> AND <expression>Looks like you have FLAG_BOOLEAN enabled on the query parser (which results in the OR operators working as expected). However the 'and' at the tail end of the query is kicking a syntax problem, which means you have FLAG_BOOLEAN_ANY_CASE turned on. Try turning that off and see what happens. J -- /--------------------------------------------------------------------------\ James Aylett xapian.org james at tartarus.org uncertaintydivision.org