Hello everyone,
I recently wondered,
why lucene's default conjunction operator is OR.
Is there a historical reason for that?
By the way,
Google and other search engines seem to use AND.
Please show me the light.
M
Actually, Google uses OR. The scoring algorithm favors documents that
match on more of the ORed terms.
On 4/16/2014 8:17 AM, Min-Uk Kim wrote:
Hello everyone,
I recently wondered,
why lucene's default conjunction operator is OR.
Is there a historical reason for that?
By the way,
Google and
In fact you have both, the documents at see looking at first time is first
the results with all words (AND) then the ORed results, which makes perfect
sense. Google sometimes marks on the result which word was not found with
a strike through.
But it is not so powerful as logical operators on
: I recently wondered,
: why lucene's default conjunction operator is OR.
: Is there a historical reason for that?
The only 'default' is in the query parser -- if you construct the
BooleanQueyr objects programatically you must always be explicit about the
Occur property of each Clause.
In
. Average users just get annoyed when the search engine is being
so picky.
-- Jack Krupansky
-Original Message-
From: Jose Carlos Canova
Sent: Wednesday, April 16, 2014 12:53 PM
To: java-user@lucene.apache.org
Subject: Re: is there a historical reason why default conjunction operator
: Re: is there a historical reason why default conjunction operator
is OR?
In fact you have both, the documents at see looking at first time is first
the results with all words (AND) then the ORed results, which makes perfect
sense. Google sometimes marks on the result which word was not found
