lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yonik Seeley <>
Subject Re: The logic of QueryParser
Date Mon, 13 Dec 2010 20:04:55 GMT
On Mon, Dec 13, 2010 at 2:51 PM, Robert Muir <> wrote:
> On Mon, Dec 13, 2010 at 2:43 PM, Yonik Seeley
> <> wrote:
>> On Mon, Dec 13, 2010 at 2:10 PM, Brian Hurt <> wrote:
>>>  I was just wondering what the logic was for defaulting to or instead of and.
>> Largely historical.  I think the original rational was that it
>> probably fit better with the traditional vector space model.
>> There's also not a good reason to change the default, given that
>> QueryParser isn't meant for end users.
> Thats pretty misleading Yonik.
> "In other words, the query parser is designed for human-entered text,
> not for program-generated text."

*shrugs*, I didn't recall that phrase... but I'm not clear if you
disagree with what I'm saying, or if you just think that it's
inconsistent with the documentation.

I think of the Lucene QueryParser like SQL. SQL is text based and also
meant for human entered text - but for either very expert users, or
programmatically created queries.  You normally don't want to pass
text from a search box directly to an SQL database or to the Lucene


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message