Skip to content

fix: use per-CF RocksDB options in drop-column-families dbtool command#3165

Draft
mlegner wants to merge 1 commit intozhewu/db-tool-drop-cffrom
mlegner/db-tool-drop-cf
Draft

fix: use per-CF RocksDB options in drop-column-families dbtool command#3165
mlegner wants to merge 1 commit intozhewu/db-tool-drop-cffrom
mlegner/db-tool-drop-cf

Conversation

@mlegner
Copy link
Contributor

@mlegner mlegner commented Mar 20, 2026

The DropStorageColumnFamiliesFromConfig command was opening the DB with identical global options for every column family. CFs with custom merge operators (aggregate_blob_info, per_object_blob_info, event_cursor, etc.) need those operators registered to replay WAL entries on open.

The `DropStorageColumnFamiliesFromConfig` command was opening the DB with
identical global options for every column family. CFs with custom merge
operators (aggregate_blob_info, per_object_blob_info, event_cursor, etc.)
need those operators registered to replay WAL entries on open.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@mlegner mlegner requested a review from halfprice March 20, 2026 14:12
@mlegner
Copy link
Contributor Author

mlegner commented Mar 20, 2026

This is just for temporary use, we'd need to make this a bit more robust as a permanent solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant