Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Thu, 5 May 2011 15:27:04 +0000 (UTC)
From: "Neil Hooey (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <1219225318.24779.1304609224185.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (SOLR-2498) Stop consolidating boosts for values
 of multivalued fields
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Stop consolidating boosts for values of multivalued fields
----------------------------------------------------------

                 Key: SOLR-2498
                 URL: https://issues.apache.org/jira/browse/SOLR-2498
             Project: Solr
          Issue Type: Improvement
    Affects Versions: 3.1, 4.0, Next
            Reporter: Neil Hooey


Currently, if you boost a value in a multivalued field during index time, the boosts are consolidated for every field, and the individual values are lost.

So, for example, given a list of photos with a multivalue field "keywords", and a boost for a keyword assigned to a photo corresponds to the number of times that photo was downloaded after searching for that particular keyword.

{code}
photo1: Photo of a cat by itself:
keywords: [ cat:600 feline:100 ]
=> boost total = 700

photo2: Photo of a cat driving a truck:
keywords: [ cat:100 feline:90 animal:80 truck:1000 ]
=> boost total = 1270
{code}

If you search for "cat feline", photo2 will rank higher, since the boost of "cat-like" words was consolidated for the "truck" boost anomoly to score a total of 1270. Whereas photo1, which has more "cat feline" downloads, only gets a score of 700, and ranks lower.

*Intuitively the boosts should be separate, so only the boosts for the terms searched will be counted.*

Given the current behaviour, you are forced to do one of the following:
1. Assemble all of the multi-values into a string, and use payloads in place of boosts.
2. Use dynamic fields, such as keyword_*, and boost them independently.

Neither of these solutions are ideal, as using payloads requires writing your own BoostingTermQuery, and defining a new dynamic field per multi-value makes searching more difficult than with mutlivalued fields.

There's a blog link that describes the current behaviour:
http://blog.kapilchhabra.com/2008/01/solr-index-time-boost-facts-2

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org