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 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 leverage or do i need to > do it manually ? > Thanks, > > > On 3/18/07, Chris Hostetter <[EMAIL PROTECTED]> wrote: >> >> : 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 that don't match all clauses -- but i'm sure >> it's possible that sometimes the tf is so high and the idf so low, that >> the score from one term can dominate. >> >> the only solution to your problem that i can think of is to write a custom >> Similarity class where tf and idf are fixed so only the coordFactor >> matters. >> >> >> >> >> -Hoss >> >>
