You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any reason why pub fn write_opt(&self, batch: WriteBatch, writeopts: &WriteOptions) takes WriteBatch by value instead of by reference? I could find no references to such a requirement (i.e. write batch becoming invalid after call to write) in the RocksDB documentation.
One use-case for keeping the WriteBatch would be when using opts.set_no_slowdown(true) combined with retries.
The text was updated successfully, but these errors were encountered:
Is there any reason why
pub fn write_opt(&self, batch: WriteBatch, writeopts: &WriteOptions)
takesWriteBatch
by value instead of by reference? I could find no references to such a requirement (i.e. write batch becoming invalid after call to write) in the RocksDB documentation.One use-case for keeping the WriteBatch would be when using
opts.set_no_slowdown(true)
combined with retries.The text was updated successfully, but these errors were encountered: