Hello ,
Thanks. That clears my doubts.Coming to the point two, Can
you please tell me which part of the Similarity takes care of the
same. Is it possible to implement in such a way that we give more
preference to "number of found terms". Also, here in our case we need
to give more importance to "length normalisation" than the default? So
any suggestions?
Thanks.
On 15 February 2010 19:50, Ahmet Arslan <iori...@yahoo.com> wrote:
>> 1) Does Solr (Lucene) consider exact match to be something
>> more important ? I mean if the query is
>> "description:organisation", then
>> which one of the following would be returned?
>> Document A, consiting
>> just "description:organisation" , where
>> as Document B consisting "description:bla bla ...
>> organisation bla
>> bla.. ". Does it consider length of the field-text while
>> ranking ?
>
> It is called length normalization which is done by default. It favors short
> documents. It punishes long documents.
>
>> 2) Let us assume that our query is "value0 field1:value1" .
>> So here,
>> if we use OR as the default operator its obvious that we
>> may get
>> results in which we might find dominating "value0" and no
>> "field1:value1" at all. We need some kind of mixture of
>> "OR" and
>> "AND", which gives more importance also for the "number of
>> keywords"
>> found. So I would like to find out whether we can edit some
>> kind of
>> boosting (or something relevant) to achieve this.
>
> Generally if a documents contains more query terms, it will get higher score.
> But it is not true all times since there are other parameters. For example a
> short document with only one query term might get higher score than a long
> document with containing two query terms.
>
> This link can be useful:
>
> http://lucene.apache.org/java/3_0_0/api/core/org/apache/lucene/search/Similarity.html
>
>
>
>
