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
The docs[2] says: "If there is one or more keys in the database matching prefix of lookup_key, RocksDB will place the iterator to the key equal or larger than lookup_key of the same prefix, as for total ordering mode."
So we manually place a fixed max key for each use entry index:
Unfortunately this does not work as expected, so we build another Index: TableReverseEntryIndex, which just use a fixed MaxFlakeTime subtract current time as reversed time. Then use forward seek, this does work.
Remove TableEntryIndex and BackwardFetchFeed until this resolved.
rocksdb default to prefixed seek:
The docs[2] says: "If there is one or more keys in the database matching prefix of lookup_key, RocksDB will place the iterator to the key equal or larger than lookup_key of the same prefix, as for total ordering mode."
So we manually place a fixed max key for each use entry index:
Unfortunately this does not work as expected, so we build another Index: TableReverseEntryIndex, which just use a fixed MaxFlakeTime subtract current time as reversed time. Then use forward seek, this does work.
Remove TableEntryIndex and BackwardFetchFeed until this resolved.
Refs issues : tecbot/gorocksdb#24 facebook/rocksdb#548
The text was updated successfully, but these errors were encountered: