Use PutVarInt instead of PutFixed while encoding stream entry value#791
Use PutVarInt instead of PutFixed while encoding stream entry value#791ShooterIT merged 7 commits intoapache:unstablefrom
Conversation
5843935 to
fab3152
Compare
I don't think it is late, since now it is only on one problem we need to concern is about open source license about these codes copied from leveldb/rocksdb. |
|
@torwig Thanks for your contribution. As @ShooterIT mentioned that we don't promise stability and compatibility before releasing, so feel free to do that. @ShooterIT Those Put|GetFixedXXX are NOT copied from rocksdb/leveldb indeed, we rewritten them into BIGENDIAN while the rocksdb is little endian, so I think it's good to keep Apache 2.0 statement only. https://github.com/facebook/rocksdb/blob/0050a73a4fb1ba52d78655b271a0f09ba1fbf7fc/util/coding_lean.h#L25 |
Co-authored-by: Twice <twice@apache.org>
Co-authored-by: Twice <twice@apache.org>
|
@git-hulk BTW, after reverting snappy version I have Cmake error on Fedora 35 However, I see that all builds you have in your CI are successful. |
There are some cmake changes from Snappy 1.1.7 to 1.1.9, @torwig Could you open an issue for this? I will fix it. |
|
And if you want to workaround it now, you can just remove |
|
@PragmaTwice I've created an issue: #792 |
|
@ShooterIT Can have a look again and merge if have no comment. |
As @ShooterIT recommended here: #745
I changed
PutFixed32toPutVarint32andGetFixed32toGetVarint32.Encoding/decoding functions were 'borrowed' from RocksDB codebase.
Obviously, this change makes it impossible to decode entries if entries were encoded with
PutFixed32(an error will be returned).Is it too late to introduce such a change?