docs: edit release note for schema change feature flag #57143
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release note (sql change): This is an empty commit meant to correct
a mistake in a merged release note in #57040. The original release
note indicates that a database administrator should toggle this
feature flag on and off using
SET CLUSTER SETTING feature.schemachange.enabled, but there
should be a '_' character so that the cluster setting would be:
SET CLUSTER SETTING feature.schema_change.enabled.
Below is the full original release note, with the typo fixed.
Release note (sql change): Adds a feature flag via cluster setting
for all schema change-related features. If a user attempts
to use these features while they are disabled, an error indicating
that the database administrator has disabled the feature is
surfaced.
Example usage for the database administrator:
SET CLUSTER SETTING feature.schema_change.enabled = FALSE;
SET CLUSTER SETTING feature.schema_change.enabled = TRUE;