dashjay commented on PR #3269: URL: https://github.com/apache/kvrocks/pull/3269#issuecomment-3717096663
@ltagliamonte-dd - For `Data Consistency`: Rocksdb should take care this, although rocksdb has not transaction, writebatch can help us put them all together. - For `Key Bloat` problem: this is a trade-off things to solve the problem between compatibility and the space. For kvrocks engine we flatten all hash keys to kvrocks for reduce the write amp, add more key for one TTL but not every key I think this is acceptable but need do more benchmark. - For `Expensive TTL Updates`: if we take one TTL as one key, put the TTL in value but not ts encoded into key, so that we just need to put the same key to engine other than (first scan, delete old, put new). - For `Breaks Point Lookups`: this must be the biggest problem, no matter where I put TTL, it's a problem. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
