-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix/integrate latest rocksb6.20+ #1
Conversation
# Conflicts: # options.go
Add support for opening a db with TTL support
Add pinnable slice
Add *DB.SetOptions().
fix GetApproximateSizes
Add GetStatisticsString method to Options
…_string add wrapper for GetOptionsFromString
fix memory leak in deleting filterpolicy and mergeoperator value
According to https://github.com/facebook/rocksdb/wiki/Setup-Options-and-Basic-Tuning#column-family-write-buffer-size default for `SetWriteBufferSize` should be `64MB` and not `4MB`
* 'master' of https://github.com/tecbot/gorocksdb: Add pinned slices Add *DB.SetOptions(). Add support for opening a db with TTL support fix GetApproximateSizes fix memory leak in deleting filterpolicy and mergeoperator value Add GetStatisticsString method to Options add wrapper for GetOptionsFromString
…dings-pr Add bindings for lowering CPU and IO priority of thread pools
…-on-armhf Workaround for Linux 32-bit build
merge master changes
…ty-c-bindings-pr Revert "Add bindings for lowering CPU and IO priority of thread pools"
use rocksdb_free
Reference: facebook/rocksdb#1095 The cst has alredy been consumed when associated with the prefix_extractor
remove compression library link flags.
CreateNewBackupFlush, when flush is set to true, flushes the WAL before creating the backup. When flush is set to false, it acts exactly like CreateNewBackup and backups the WAL in a separate, non-atomic operation.
Backup improvements
Adjust go versions in travis
Add missing table options and full bloom filter
Attempting to destroy the opts.cst will segfault
Add function to create MemEnv
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we maintaining a fork when there are no changes, or if some changes we need why arent we contributing to the upstream & increasing our tech debt?
some patches are added on the fork. see 9721107 |
only 6.20.3 works on Apple M1 chip. but gorocksdb is broken by rocksdb public api changes since v6.16.0 https://github.com/facebook/rocksdb/blob/e8f116deabc601a5eae011f2fd8a38d02d87be8d/HISTORY.md#public-api-change-13
if we want to debug sharder on Apple M1 chip, rocksdb has to be upgraded to v6.20.3, and @ssardana08 could you try to send a PR to tecbot/gorocksdb too? we can drop our fork if it is fixed on tecbot/gorocksdb |
@cnlangzi look like there is already a PR opened for the same since March 2021 on the upstream, but not merged |
Lets get it in since the fork as well as the main library has not been maintained. |
No description provided.