Repository Pattern - findAll pagination returns inconsistent result with redis read replicas

[sureshkmit]

Sample Usage:

    Example entity = Example.of(entityAttributes);
    final Pageable pageable = Pageable.ofSize(pageSize).withPage(pageNumber);
    return repository.findAll(entity, pageable);

Redis set data type doesn't guarantee the element order when retrieved from replica. As the keys returned by the findKeys method in RedisQueryEngine are not ordered, it causes issues when applying subList for pagination, especially with Redis read replicas. To ensure consistent pagination, the list of keys should be sorted before sublisting.

RedisQueryEngine.java#L118

[christophstrobl]

Thank you for getting in touch. We'd appreciate if you can take the time to provide a complete minimal sample (something that we can unzip or git clone, build, and deploy) that reproduces the problem.

[spring-projects-issues]

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

[manoshreejj]

We were able to replicate the issue in elasticache, will get back to you with a minimal sample code with local redis setup shortly.

[christophstrobl]

@manoshreejj thank you. Please note that the issue needs to be reproducible with Redis. Other distributions are only supported on a best-effort basis (see also: #3124).