Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SET should fail for config that cannot be changed in a session #7156

Closed
mjsax opened this issue Mar 4, 2021 · 1 comment
Closed

SET should fail for config that cannot be changed in a session #7156

mjsax opened this issue Mar 4, 2021 · 1 comment
Assignees
Labels
core-infra Issues owned by the ksqlDB Core Infra team enhancement fix-it-week P1 Slightly lower priority to P0 ;)
Milestone

Comments

@mjsax
Copy link
Member

mjsax commented Mar 4, 2021

Is your feature request related to a problem? Please describe.
Using set command, it is possible to change config that cannot be changed dynamically, for example ksql.schema.registry.url. Issuing a corresponding set command just report success and show properties shows the new value, even if the new value is not effective.

Describe the solution you'd like
The set command should fail with a descriptive error message if the config cannot be changes, and show properties should still show the old value.

@mjsax mjsax changed the title SET should fail for config that cannot be changes in a session SET should fail for config that cannot be changed in a session Mar 4, 2021
@rodesai
Copy link
Contributor

rodesai commented Mar 10, 2021

related: #6869

@rodesai rodesai added core-infra Issues owned by the ksqlDB Core Infra team P1 Slightly lower priority to P0 ;) fix-it-week and removed needs-triage labels Mar 10, 2021
@rodesai rodesai added this to the 0.18.0 milestone Mar 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core-infra Issues owned by the ksqlDB Core Infra team enhancement fix-it-week P1 Slightly lower priority to P0 ;)
Projects
None yet
Development

No branches or pull requests

3 participants