So you're saying that you have B_1 - B_8 in one doc, B_9 - B_16 in another doc etc?
What's so confusing is that in your first e-mail, you said: bq: This denormalization grows the index size with a factor 100 in worse case. Which I took to mean you have at most 100 of these fields. Please look at the function query page I referenced and try a few things so we can deal with specific questions. You can put the results of a _query_ in a function query, so you could probably just form a sub-query that returns a score that you in turn use to boost the doc. Best, Erick On Thu, Apr 10, 2014 at 8:04 AM, StrW_dev <r.j.bamb...@structweb.nl> wrote: > Erick Erickson wrote >> Well, you're constructing the URL somewhere, you can choose the right >> boost there can't you? > > Yes of course! > > As example: > We have one filter field called FILTER which can have unlimited values acros > all documents. > Each document as on average 8 values set for FILTER (e.g. FILTER > ["1","2",..,"8"]). > So we could add boost fields depending on each of these values as B_1:1.0, > ... ,B_7:5.0 for example and use that during query time. This is your > suggestions correct? > > So each document has on average 8 of these dynamic fields, while over the > whole index we have unlimited of these fields. What would this mean for the > performance? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Shared-Stored-Field-tp4130351p4130411.html > Sent from the Solr - User mailing list archive at Nabble.com.
