You can make a separate facet field which contains a range of "buckets": 10, 20, 50, or 100 means that the field has a value 0-10, 11-20, 21-50, or 51-100. You could use a separate filter query with values for these buckets. Filter queries are very fast in Solr 1.4 and this would limit your range query execution to documents which match the buckets.
But, in general, this is a "shopping cart" database and Solr/Lucene may not be the best fit for this problem. If you want to do numerical analysis on your shopping carts, check out KNIME: www.knime.org . It's wonderful. On Wed, Dec 2, 2009 at 8:38 AM, gdeconto <gerald.deco...@topproducer.com> wrote: > > I dont believe there is any way to link values in one multivalue field to > values in other multivalue fields. > > Re "where each doc contains the customer info and info for ALL products that > the customer might have (likely done via dynamicfields)": > > one thing you might want to consider is that this solution might lead to > performance issues if you need to do range queries such as q=((Width1:[50 TO > *] AND Density1:[7 to *]) OR (Width2:[50 TO *] AND Density2:[7 TO *]) OR …) > > I had a similar problem a while back, and basically had similar options. In > my tests, this particular option became slower as I increased the number of > "products" (and so the number of unique values for each "product" field). > > If you come up with a solution, let me know. > > also, another option might be to encode the "product" information (ie using > a field delimiter, something like CSV) and then storing it into a multivalue > field for each customer. I dont know how you would search that data tho > (maybe by having a unique delimiter for each field?) > -- > View this message in context: > http://old.nabble.com/question-about-schemas-tp26600956p26611997.html > Sent from the Solr - User mailing list archive at Nabble.com. > > -- Lance Norskog goks...@gmail.com
