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
Most relevant classes: CollationController, SSTableNamesIterator.
At present, AtlasDB uses the SliceQueryFilter for its queries. This has three downsides.
In multicolumn range scans, we must read all historic versions.
Cassandra has an optimization for the names query filter - it says - sort your SSTables by max timestamp descending (provided that they do not overlap) - if you see the relevant column in the latest SSTable, you can skip looking at the others.
We can only select one column per RPC - if an internal use case has 5 columns, we must issue 5 RPCs to Cassandra in order to load these.
It would be relatively straightforward for us to define an AtlasDBQueryFilter which specializes Cassandra's behaviour for AtlasDB tables specifically - locating the latest write for the cell only instead of having to look at all SSTables and merge.
The text was updated successfully, but these errors were encountered:
Most relevant classes: CollationController, SSTableNamesIterator.
At present, AtlasDB uses the SliceQueryFilter for its queries. This has three downsides.
It would be relatively straightforward for us to define an AtlasDBQueryFilter which specializes Cassandra's behaviour for AtlasDB tables specifically - locating the latest write for the cell only instead of having to look at all SSTables and merge.
The text was updated successfully, but these errors were encountered: