thustorage/Sherman

Why range query marked with "need fix"?

Closed this issue · 2 comments

Hello!I wonder why range query is not completed. Does it have to support version consistency when doing the range query which may cost a long time? I would aslo like to know why you don't use sibling pointer when doing range query.

The current implementation is a simplified version with the assumption that all innernal nodes are cached in compute nodes:

// FIXME: here, we assume all innernal nodes are cached in compute node

It does cause the anomalies that some kv entries are miss in the results when inserting new keys (updating keys will not induce the anomalies). We will fix it when we have time.

OK,thanks!