-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update RocksDB to 9.0.0 #39
Conversation
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.
Sorry I got wrapped around the axle, roxide-rocksdb
is from the upstream rocksdb
code base, I assume you pulled in the latest version and that's what all of those diffs are from. I couldn't figure out why the code base was so weird and unfamiliar.
Ignore my questions, this LGTM.
roxide-rocksdb/src/column_family.rs
Outdated
} | ||
|
||
/// An opaque type used to represent a column family. Returned from some functions, and used | ||
/// in others | ||
pub struct ColumnFamily { | ||
pub(crate) inner: *mut ffi::rocksdb_column_family_handle_t, | ||
pub inner: *mut ffi::rocksdb_column_family_handle_t, |
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.
Yikes, why are the inner
pointers all public now?
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.
I've accidentally overdid it. They are pub(crate)
in the original repo, but in some of these structs you've explicitly changed access to pub
to use in roxide
. I'll revert this and leave only those which are really needed
Part of https://github.com/elastio/scalez/issues/641