Oops, fat fingers.
see:
searchhub.org/2012/02/23/date-math-now-and-filter-queries/
If you're not re-using the _same_ filter query, you'll be better
off using fq={!cache=false}range_query
Best,
Erick
On Mon, May 30, 2016 at 8:16 PM, Erick Erickson <erickerick...@gmail.com> wrote:
> That does seem long, but you haven't provided many details
> about the fields. Are there 100 docs in your index? 100M docs? 500M docs?
>
> Are you using NOW in appropriately? See:
>
> On Fri, May 27, 2016 at 1:32 PM, Jay Potharaju <jspothar...@gmail.com> wrote:
>> Hi,
>> I am running filter query(range query) on date fields(high cardinality) and
>> the performance is really bad ...it takes about 2-5 seconds for it to come
>> back with response. I am rebuilding the index to have docvalues & tdates
>> instead of "date" field. But not sure if that will alleviate the problem
>> because of high cardinality.
>>
>> Can I store the date as YYYYMMDD and run range queries on them instead of
>> date fields?
>> Is that a good option?
>>
>> --
>> Thanks
>> Jay
