Ruixiang Tan
Ruixiang Tan
@IoCing Hi. You can merge the newest unstable branch, and compile again.
LGTM. Thank you very much for your contribution.
> > Thanks for your clarification. It makes sense to export the value size of the specific key, and it should be possible since the RocksDB has a way to...
@PragmaTwice Hi. Do you have any more suggestions on reducing redundant code?
@PragmaTwice @git-hulk @torwig I noticed a problem. In the following tests. When we write a value with only one bit(like 'a'). Occasionally, the size of the key we get is...
> @PragmaTwice @git-hulk @torwig I noticed a problem. In the following tests. When we write a value with only one bit(like 'a'). Occasionally, the size of the key we get...
> > > @PragmaTwice @git-hulk @torwig I noticed a problem. In the following tests. When we write a value with only one bit(like 'a'). Occasionally, the size of the key...
Is it possible that it is a bug of rocksdb? I can get the value of the corresponding key, but the size occupied by the key is 0. And this...
> > > > > @PragmaTwice @git-hulk @torwig I noticed a problem. In the following tests. When we write a value with only one bit(like 'a'). Occasionally, the size of...
> OK, got it. I need to read this PR first and try to reproduce it on my side. @git-hulk I used the parameters configured for `GetApproximateSizes` testing in `rocksdb`....