[server] Fix alter cluster configs - #4179
Conversation
|
@leekeiabstraction just one nit:
Otherwise LGTM, and we can merge once CI is green. |
Tightens the authorization performed when altering certain dynamic cluster-config keys, and adds an integration test covering the behavior. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AMMDkWCsb8fPv4V4upvzcy
75699a4 to
02a2bb8
Compare
|
@leekeiabstraction Hi Keith, I saw your PR: #4179. Are you currently using Fluss in production, and is this change intended to address a production safety concern? I’m asking because it may break compatibility with my existing production deployment, in which case I may need to roll back the change(#4196). If you need this in production, maybe we could add a configuration flag in a follow-up to preserve backward compatibility later. |
Improve mechanism around altering certain dynamic cluster-config keys, and adds an integration test covering the behavior.