Search before asking
Motivation
I found that log.segment.file-size currently only respects server-level configurations and is ignored when defined at the table level. I would like to propose a mechanism that allows the system to prioritize table-specific configurations if they exist, falling back to the global server options only as a default. This would provide better flexibility for handling tables with unique throughput or storage requirements.
Solution
No response
Anything else?
No response
Willingness to contribute
Search before asking
Motivation
I found that
log.segment.file-sizecurrently only respects server-level configurations and is ignored when defined at the table level. I would like to propose a mechanism that allows the system to prioritize table-specific configurations if they exist, falling back to the global server options only as a default. This would provide better flexibility for handling tables with unique throughput or storage requirements.Solution
No response
Anything else?
No response
Willingness to contribute