Yep, I get it. But from the tests I did it tips it enough for those
cases to be rare (and probably justified).
Thx
On 3/19/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: wouldn't doing something like this in the query :
: (field1:tag1 tag2) OR (field1:tag1 AND tag2)
: The documents that have
: wouldn't doing something like this in the query :
: (field1:tag1 tag2) OR (field1:tag1 AND tag2)
: The documents that have all the tags (tag1 and tag2) will comply with
: both conditions and get scores from both while the documents that
: don't have both tags will only get a score from the 1st
An example would help. A query and the results that you see.
wunder
On 3/18/07 6:48 PM, "shai deljo" <[EMAIL PROTECTED]> wrote:
> I assumed the tf/idf would behave like this but it's behaving VERY
> differently/wrong so i wonder maybe something is wrong with my
> indexing strategy ?
> I think fo
Hey Chris,
wouldn't doing something like this in the query :
(field1:tag1 tag2) OR (field1:tag1 AND tag2)
Achieve similar affect ?
The documents that have all the tags (tag1 and tag2) will comply with
both conditions and get scores from both while the documents that
don't have both tags will on
I assumed the tf/idf would behave like this but it's behaving VERY
differently/wrong so i wonder maybe something is wrong with my
indexing strategy ?
I think for a quicker solution (ok, hack :) ) I'll run two different
queries (AND, OR) and merge them.
Does SOLR support some kind of merging i can
: How do i force SOLR to score documents that contain ALL terms 1st
: before results that contain some of the terms?
generally speaking this is hte result you will usually on random data ...
under the covers Lucene uses TF/IDF based weighting of terms, with a coord
factor that penalizes queries t
