On Mon, Dec 13, 2010 at 3:16 PM, Yonik Seeley
wrote:
> On Mon, Dec 13, 2010 at 3:07 PM, Robert Muir wrote:
>> On Mon, Dec 13, 2010 at 3:04 PM, Yonik Seeley
>> wrote:
>>> I think of the Lucene QueryParser like SQL. SQL is text based and also
>>> meant for human entered text - but for either very
On Mon, Dec 13, 2010 at 3:07 PM, Robert Muir wrote:
> On Mon, Dec 13, 2010 at 3:04 PM, Yonik Seeley
> wrote:
>> 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 n
On Mon, Dec 13, 2010 at 3:04 PM, Yonik Seeley
wrote:
> 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
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 origina
On Mon, Dec 13, 2010 at 2:35 PM, Ahmet Arslan wrote:
> > I have googled the mailing list archives and didn't find
> > anything. But if
> > this has been discussed to death, please just point me to
> > the threads in the
> > archive. rather than stirring up some old flame war.
> > Or just tell me
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
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 t
On Mon, Dec 13, 2010 at 2:10 PM, Brian Hurt wrote:
> I just encountered an unexpected behavior in query parser. So, if you pass
> in a query that is multiple terms, like "cat hat", the query that is
> returned uses an or between the two term searches, instead of an and. That
> is, the query will
> I have googled the mailing list archives and didn't find
> anything. But if
> this has been discussed to death, please just point me to
> the threads in the
> archive. rather than stirring up some old flame war.
> Or just tell me what
> to google for (the terms I've tried haven't yielded
> anyt
I just encountered an unexpected behavior in query parser. So, if you pass
in a query that is multiple terms, like "cat hat", the query that is
returned uses an or between the two term searches, instead of an and. That
is, the query will return all documents with the given field containing
either
10 matches
Mail list logo
