Add support for dropping tables#5
Add support for dropping tables#5hashbrowncipher wants to merge 3 commits intoInstagram:rocks_3.0from
Conversation
Otherwise old columnfamily data could conflict with new columnfamily data
|
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need the corporate CLA signed. If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
|
Thanks for contributing! Do you mind rebasing -- we've since added optional RocksDB shards within the RocksDBCF so there are multiple instances where the table needs to be dropped. Can you also provide a more concrete migration path for users with existing non-UUID filepaths? |
This branch enables support for dropping tables. In addition do that, it: