Aggregation vs Search/Filter discrepancy - caching issue?


#1

I have a test that indexes some data, does an aggregation + search to
verify the results.
Then my test changes 1 piece of data and re-indexes (everything).
refresh() is called.

Then I do an aggregation + search again to verify my results.
The search results are correct (ie updated to reflect the changed data).
The aggregation results are not correct - they are the same as the first
aggregation results - implying the data has not changed.
The aggregation results go wrong at the result of a filter aggregation. The
results of the filter aggregation give a count of 2 - the results of the
search (equiv query or same filter) give 1.

Suspecting a caching issue (e.g. filter caching) I then made sure I flushed
the caches for that index. But sadly, the problem still persists.

I am kinda running out of ideas. Can anyone suggest what to check next?

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/61140ef1-441f-477d-8129-d30588b6838b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


#2

Update elastic to 1.2 - still seeing the same issue...

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/2805708d-57dd-4977-a17c-2c27d9ee98d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(Adrien Grand) #3

Can you share your test case?

On Tue, Jun 3, 2014 at 1:00 PM, mooky nick.minutello@gmail.com wrote:

Update elastic to 1.2 - still seeing the same issue...

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/2805708d-57dd-4977-a17c-2c27d9ee98d0%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/2805708d-57dd-4977-a17c-2c27d9ee98d0%40googlegroups.com?utm_medium=email&utm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
Adrien Grand

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAL6Z4j7T%2B%3DgXO%2BGHGFw11RBjpTOkXCUJ%2Bz2yVauU_YOo6Pmwxg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


#4

Turns out it was user error. Please ignore.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/81ca5558-4fd3-44cd-ae72-4490145fa905%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(system) #5