Yu Zhang

Thanks for the request. This feature is not on our recent roadmap. A workaround would be if your primary instance can communicate with the secondary instance somehow when a new...

> 2\. 2b) Register the DB/CF with an event listener that implements `OnMemTableSealed()`, which also calls `IncreaseFullHistoryTsLow(/* some ts representing now */)` Thanks for this detailed alternative proposal. My understanding...

> If the user wanted loose retention by default and minimal retention only during Flush() and CompactRange(), they could dynamically set it accordingly. This is a great idea! It seems...

> How does the user specify the callback? In `WriteOptions` perhaps? Yeah, that's a good question. `WriteOptions` would work, another idea is maybe we can make `WriteWithCallback` a public API...

> LGTM! Thanks for the PR and quick turnaround Thank you for the quick review!

> @jowlyzhang Can you check this PR? Thanks for making the changes. Since this PR now mostly have java changes, I'll leave it to @adamretter to make the call here.

@swamirishi Thank you for this work! Just curious, is the motivation for this class to be able to read the sequence number and type of each entry from a table...

> Currently the db_iter skips non user keys > > https://github.com/facebook/rocksdb/blob/003197f0050b8ef3d52d2c291401991a562c773c/db/db_iter.cc#L289 > > , currently the sst file reader is tightly coupled with this. sst file reader should be returning...

https://github.com/facebook/rocksdb/blob/cb4f4381f6d3f00b81e693f602839536261ee5f6/table/sst_file_reader.cc#L94 > > makes it a db_iter I see, so you need an iterator to pragmatically iterate the raw sst file to get the tombstone. So you want to define...

> We actually wanted a jni which would let us iterate through the sst file and get the key,value, sequenceNumber for each of the records including the tombstone entries from...