Closed ltworf closed 8 years ago
@colings86 it looks like the script is being cached along with the field datatype lookup? Please could you take a look.
@colings86 has this already been fixed?
@clintongormley I'm not aware of any fix that has been merged for this. I have also just tried to reproduce it without success.
@ltworf are you still able to reproduce this bug on the latest version of Elasticsearch (currently 2.1)?
I no longer work on that project. I will unsubscribe this.
OK - I'll close for now as presumed fixed
It took me a little while to narrow down this bug.
I have a cluster with various indexes and types, and I have a query that performs aggregations, that only works on one index/type and fails miserably if executed on anything else.
This is the query I use:
And this is an example of document inside the type
Now the problem is that if I try to run the query on
/
, I will get some exceptionsAfter the exceptions, if I run the query on the correct index/type, the aggregations on the years and decades will work fine, however if I run the query on
/
as first thing after starting elasticsearch, then subsequent correct queries will fail to aggregate years and decades, which will only contain empty data structures in the response.Let me know if you need more information.