Changing the limit/offset of a query does not clear the cached results

Description

I didn't check with a test, but from what I can see, calling firstResult/maxResult on HSQueryImpl does not clear the cached results, so I think using paging repeatedly on the same query instance will always return the same result size...

Environment

None

Activity

Show:
Yoann Rodière
August 10, 2017, 8:06 AM

Well... As usual I went ahead of myself: the result size is meant to be the total result size, ignoring pagination. So it's not affected by the offset nor by the limit.

Yoann Rodière
August 10, 2017, 8:13 AM

Just this once, I was wrong to say I was wrong. In the Elasticsearch case, we cache not only the result size, but also the search hits, so not clearing the cache when the limit/offset is changed actually hurts.

Assignee

Yoann Rodière

Reporter

Yoann Rodière

Labels

None

Suitable for new contributors

None

Feedback Requested

None

Components

Fix versions

Affects versions

Priority

Major
Configure