Re: Price Range Faceting Based on Date Constraints

2015-05-22 Thread alexw
That's awesome! Thanks David. By the way, I own a copy of your terrific book (Solr Enterprise Search Server) and am a big fan. Alex Wang Technical Architect Crossview, Inc. C: (647) 409-3066 aw...@crossview.com On Thu, May 21, 2015 at 11:40 PM, david.w.smi...@gmail.com [via Lucene] < ml-node+s472

Re: Price Range Faceting Based on Date Constraints

2015-05-21 Thread david.w.smi...@gmail.com
Indeed: https://github.com/dsmiley/SOLR-2155 On Thu, May 21, 2015 at 8:59 PM alexw wrote: > Thanks David. Unfortunately we are on Solr 3.5, so I am not sure whether > RPT > is available. If not, is there a way to patch 3.5 to make it work? > > > > -- > View this message in context: > http://luce

Re: Price Range Faceting Based on Date Constraints

2015-05-21 Thread alexw
Thanks David. Unfortunately we are on Solr 3.5, so I am not sure whether RPT is available. If not, is there a way to patch 3.5 to make it work? -- View this message in context: http://lucene.472066.n3.nabble.com/Price-Range-Faceting-Based-on-Date-Constraints-tp4206817p4207003.html Sent from the

Re: Price Range Faceting Based on Date Constraints

2015-05-21 Thread David Smiley
Another more modern option, very related to this, is to use DateRangeField in 5.0. You have full 64 bit precision. More info is in the Solr Ref Guide. If Alessandro sticks with RPT, then the best reference to give is this: http://wiki.apache.org/solr/SpatialForTimeDurations ~ David https://www

Re: Price Range Faceting Based on Date Constraints

2015-05-21 Thread alexw
Thanks Holger and Alessandro, SpatialRecursivePrefixTreeFieldType is a new concept to me, and I need some time to dig into it and see how it can help solve my problem. Alex Wang Technical Architect Crossview, Inc. C: (647) 409-3066 aw...@crossview.com On Thu, May 21, 2015 at 11:50 AM, Holger Rie

Re: Price Range Faceting Based on Date Constraints

2015-05-21 Thread Alessandro Benedetti
Just thinking a little bit on it, I should investigate more the . SpatialRecursivePrefixTreeFieldType . Each value of that field is it a Point ? Actually each of our values must be the rectangle. Because the time frame and the price are a single value ( not only the duration of the price 'end dat

Re: Price Range Faceting Based on Date Constraints

2015-05-21 Thread Alessandro Benedetti
The geo-spatial idea is brilliant ! Do you think translating the date into ms ? Alex, you should try that approach, it can work ! Cheers 2015-05-21 16:49 GMT+01:00 Holger Rieß : > Give geospatial search a chance. Use the > 'SpatialRecursivePrefixTreeFieldType' field type, set 'geo' to false. > T

Re: Price Range Faceting Based on Date Constraints

2015-05-21 Thread alexw
Hi Alex, Thanks for the link to the presentation. I am going through the slides and trying to figure out the time-sensitive search it talks about and how it relates to the problem I am facing. It looks like it tries to solve the problem of sku availability based on date, while in my case, all skus

Re: Price Range Faceting Based on Date Constraints

2015-05-21 Thread alexw
Thanks Alessandro. I am implementing this in the Hybris framework. It is not easy to create nested documents during indexing using the Hybris Solr indexer. So I am trying to avoid additional documents and cores if at all possible. -- View this message in context: http://lucene.472066.n3.nabble.

Re: Price Range Faceting Based on Date Constraints

2015-05-21 Thread Alexandre Rafalovitch
Did you look at Gilt's presentation from a while ago: http://www.slideshare.net/trenaman/personalized-search-on-the-largest-flash-sale-site-in-america Slides 33 on might be most relevant. Regards, Alex. Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter: http://www.solr-start

Re: Price Range Faceting Based on Date Constraints

2015-05-21 Thread Alessandro Benedetti
Hi Alex, this is not a simple problem. In your domain we can consider a Product as a document and the list of nested Documents. Ideally we would model the Product as the father and the prices as children. Each will be defined by : - *start_date * - *end_date * - *price * - *productI