As a user I want to have consistent results when sorting records exceeding the defaultchunksize of 1000.
Description:
With the pagination changes applied, a single search request serves 1000 records to the frontend. Any sorting is applied within these 1000 records but is not applied redis. Thus when loading more records from redis (aka a new api page or chunk) the sorting is not applied. This can be solved by sending the sorting direction to the backend and sort the result there. Downside is, that any sorting comes at the costs of an additonal call (around 5 secs waiting time)
User story
As a user I want to have consistent results when sorting records exceeding the defaultchunksize of 1000.
Description:
With the pagination changes applied, a single search request serves 1000 records to the frontend. Any sorting is applied within these 1000 records but is not applied redis. Thus when loading more records from redis (aka a new api page or chunk) the sorting is not applied. This can be solved by sending the sorting direction to the backend and sort the result there. Downside is, that any sorting comes at the costs of an additonal call (around 5 secs waiting time)