My team may soon be required to return search results for a large index of products ranked by price ascending or descending. The documentation is very clear that every sort order requires its own replica index, but we don’t have the capacity without purchasing an additional cluster.
I have two questions:
Why can’t Algolia support inverting sort orders on the same index? I understand why supporting multiple different sort orders would not be compatible with your algorithm, but inverting seems so simple to implement.
We are considering implementing an inverse sort by running a dummy query to get the number of hits, then requesting the pages from last to first. Is there a cleaner way to implement this at query time via the search API?