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
It has been a while since we last updated rdb_i_s_cfoptions_fill_table function. As a result, information_schema.ROCKSDB_CF_OPTIONS table returns limited number of CF options, while we can dynamically update CF options that don't exist in the i_s table. This is confusing. For example, you can change max_compaction_bytes dynamically, but the only way to confirm the change is reading LOG file.
SET @@global.rocksdb_update_cf_options = 'default={max_compaction_bytes=4026531840};';
SELECT * FROM ROCKSDB_CF_OPTIONS WHERE CF_NAME='default' AND OPTION_TYPE='max_compaction_bytes';
-> empty set
LOG shows max_compaction_bytes changed.
It has been a while since we last updated rdb_i_s_cfoptions_fill_table function. As a result, information_schema.ROCKSDB_CF_OPTIONS table returns limited number of CF options, while we can dynamically update CF options that don't exist in the i_s table. This is confusing. For example, you can change max_compaction_bytes dynamically, but the only way to confirm the change is reading LOG file.