Hmmm, I scanned your question, so maybe I missed something. It sounds like you have a fixed number of filters known at index time, right? So why not index these boosts in separate fields in the document (e.g. f1_boost, f2_boost etc) and use a function query (https://cwiki.apache.org/confluence/display/solr/Function+Queries) at query time to boost by the correct one?
Of course I may be waaaay off base here, but.... BTW, you could use dynamic fields to not have to pre-define the maximum number of boost fields, something like this in my example: <dynamicField name="*_boost" type="float" indexed="true" stored="false"/> Best Erick On Thu, Apr 10, 2014 at 4:30 AM, StrW_dev <r.j.bamb...@structweb.nl> wrote: > Hello, > > We have a denormalized index where certain documents point in essence to the > same content. > The relevance of the documents depends on the current context. E.g. document > A has a different boost factor when we apply filter F1 compared to when we > use filter F2 (or F3, etc). > To support this we denormalize document A with a unique boost field, such > that for each filter he can be found in he has a different relevance. > > The problem is that the documents have a big stored content that is required > for the highlighting snippets. > > This denormalization grows the index size with a factor 100 in worse case. > Storing the same big content field a lot of times times seems really > inefficient. > Is there a way to point a group of documents to the same stored content > fields? > Or is there a different way to influence the relevance depending on the > current search context? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Shared-Stored-Field-tp4130351.html > Sent from the Solr - User mailing list archive at Nabble.com.
