Re: Use default field, if more specific field does not exist

2016-04-03 Thread Georg Sorst
Hi Emir, could this be done with Pivot faceting? The idea is to use facet.pivot=price_USER_ID,price. Then I should get all values + number of matching documents for price_USER_ID (sub-faceted by price, which I can just ignore). Additionally, there should be one facet value for price_USER_ID for a

Re: Use default field, if more specific field does not exist

2016-03-28 Thread Emir Arnautovic
Hi Georg, I cannot think of similar trick that would enable you to facet on all values (other than applying this trick to buckets of size 1) but would warn you about faceting of high cardinality fields such as price. Not sure if you have some specific case, but calculating facet for such field

Re: Use default field, if more specific field does not exist

2016-03-26 Thread Georg Sorst
Hi Emir, that sounds like a great idea and filtering should be just fine! In our case we need the individual price values (not the buckets), just like facet.field=price but with respect to the user prices. Is this possible as well? About the performance: Are there any specific bottlenecks you wo

Re: Use default field, if more specific field does not exist

2016-03-25 Thread Emir Arnautovic
Hi Georg, One solution that could work on existing schema is to use query faceting and queries like (for USER_ID = 1, bucker 100 to 200): price_1:[100 TO 200] OR (-price_1:[* TO *] AND price:[100 TO 200]) Same query is used for filtering. What you should test is if performances are acceptable

Use default field, if more specific field does not exist

2016-03-24 Thread Georg Sorst
Hi list, we use Solr to search ecommerce products. Items have a default price which can be overwritten per user. So when searching we have to return the user price if it is set, otherwise the default price. Same goes for building facets and when filtering by price. What's the best way to achieve