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-D
ssage in context:
> http://lucene.472066.n3.nabble.com/Price-Range-Faceting-Based-on-Date-Constraints-tp4206817p4207003.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
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
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
t;
>
> Faceting possibly can be done with a facet query for every of your price
> ranges.
> For example day 20, price range 0-5$, rectangle: 20.0
> 0.0 21.0 5.0.
>
> Regards Holger
>
>
>
> --
> If you reply to this email, your message will b
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
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
Give geospatial search a chance. Use the 'SpatialRecursivePrefixTreeFieldType'
field type, set 'geo' to false.
The date is located on the X-axis, prices on the Y axis.
For every price you get a horizontal line between start and end date. Index a
rectangle with height 0.001(< 1 cent) and width 'en
skus are
available, but the prices are time-sensitive, and faceting logic needs to
pick the right price for each sku when counting.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Price-Range-Faceting-Based-on-Date-Constraints-tp4206817p4206856.html
Sent from the Solr - User
.nabble.com/Price-Range-Faceting-Based-on-Date-Constraints-tp4206817p4206854.html
Sent from the Solr - User mailing list archive at Nabble.com.
ight as to how the index should be designed and what the
> facet query should look like?
>
> Thanks in advance for your help!
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Price-Range-Faceting-Based-on-Date-Constraints-tp4206817.html
> Sent from the Solr - User mailing list archive at Nabble.com.
query should look like?
>
> Thanks in advance for your help!
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Price-Range-Faceting-Based-on-Date-Constraints-tp4206817.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
http://lucene.472066.n3.nabble.com/Price-Range-Faceting-Based-on-Date-Constraints-tp4206817.html
Sent from the Solr - User mailing list archive at Nabble.com.
13 matches
Mail list logo