weimingdiit commented on PR #7117: URL: https://github.com/apache/ozone/pull/7117#issuecomment-2319741029
> Hi @weimingdiit thanks for looking in to this. Maybe it would be better to support RocksDB config files directly instead of needing to expose each config through the Ozone configuration? See the [RocksDB docs](https://github.com/facebook/rocksdb/wiki/RocksDB-Options-File) on this for reference. We could first load the options set by the user in this file, and then override any in Ozone that must be set a certain way, for example creating column families that don't exist. Thank you very much for your comments，this is a good idea. However, for the current version, could we first make some of the more performance-critical parameters configurable, such as the ones I mentioned? I will continue to follow up on this issue and create a new issue to directly support RocksDB configuration files, so we don't have to rely on Ozone configuration. What do you think? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
