You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 1, 2023. It is now read-only.
Currently chogori platform does not support descending storage layout, and for chogori SQL we will disallow descending secondary indexes and descending primary indexes will need to be sorted and handled in the PG layer.
The difficulty with descending storage layout is that we support compound keys which are encoded together in a single string, which gives better performance than per key-field comparison and makes range partitioning easier. The problem is how to encode variable length string fields in reverse order (perhaps we can check the ELEN paper for a solution). If it is not possible than a complete solution would require re-writing the platform layer to handle keys per-field everywhere.
Some other partial solutions:
Support descending order for key fields that are not strings only
In SQL K2 adapter layer, we can transparently use a reverse order scan if there is only one primary key or the other primary keys are fully specified.
The text was updated successfully, but these errors were encountered:
Currently chogori platform does not support descending storage layout, and for chogori SQL we will disallow descending secondary indexes and descending primary indexes will need to be sorted and handled in the PG layer.
The difficulty with descending storage layout is that we support compound keys which are encoded together in a single string, which gives better performance than per key-field comparison and makes range partitioning easier. The problem is how to encode variable length string fields in reverse order (perhaps we can check the ELEN paper for a solution). If it is not possible than a complete solution would require re-writing the platform layer to handle keys per-field everywhere.
Some other partial solutions:
The text was updated successfully, but these errors were encountered: