Test it and see :)
But it's more whether it'll achieve your goal or not as I imagine the
performance difference is negligible. But test and see (and report back please)
> On Jan 24, 2016, at 20:35, Jay Potharaju wrote:
>
> Which is a better option facet.interval or facet.query in terms of
> pe
Which is a better option facet.interval or facet.query in terms of
performance?
Thanks
On Sun, Jan 24, 2016 at 5:04 PM, Erik Hatcher
wrote:
> I suggest facet.query is the way to go for a handful of buckets/ranges.
>
> I'm mobile so apologies for not providing some examples but something like
>
I suggest facet.query is the way to go for a handful of buckets/ranges.
I'm mobile so apologies for not providing some examples but something like a
few of these kinds of things:
facet.query={!lucene key=under_24_hours}update_date:[NOW-24HOURS TO NOW]
Things get interesting if you want < 3
Thanks Pavel,
I was trying it using the range faceting instead of facet.interval. Can
someone comment on performance of using facet.interval with sharded index
and high number of documents.
Thanks
J
On Sun, Jan 24, 2016 at 1:09 PM, Pavel Polívka
wrote:
> Hi,
> We are doing this via interval fac
Hi,
We are doing this via interval facet:
Something like this:
facet=on&
facet.interval=update_date&
facet.interval.set=[NOW-1DAY,NOW]&
facet.interval.set=[NOW-3DAY,NOW-1DAY)&
facet.interval.set=[NOW-7DAY,NOW-3DAY)&
facet.interval.set=[NOW-1MONTH,NOW-7DAY)&
facet.interval.set=[NOW-1YEAR,NOW-1MONTH
Hi,
I am trying to calculate facet for update_date of the document. And would
like to get the following values
- < 24 Hrs
- < 3 days
- < 1 week
- < 1 month
- < 6 months
- <1 year
The above facet values should change every time someone queries, therefore
a document that was updated today will s
