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

sql,multiregionccl: rename multiregion system DB cluster setting #122285

Merged
merged 1 commit into from
May 8, 2024

Conversation

rafiss
Copy link
Collaborator

@rafiss rafiss commented Apr 12, 2024

Avoid using the word "preview" in the name. That shouldn't be needed, since the cluster setting is hidden, so users would only know about it if we tell them to enable it. Keeping "preview" in the name isn't a huge problem, but it's just slightly annoying if we decide that we want to keep the setting around even after the feature leaves the "preview" status, since it requires updating docs and any customer code that was using the old name.

Also, this removes the mention of the setting in error messages. An error should not refer to an undocumented setting, since a user would have no way of learning more about it.

informs: #63365
Epic: CRDB-33032
Release note: None

@rafiss rafiss requested a review from fqazi April 12, 2024 14:24
@rafiss rafiss requested review from a team as code owners April 12, 2024 14:24
@rafiss rafiss requested review from herkolategan and renatolabs and removed request for a team April 12, 2024 14:24
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Avoid using the word "preview" in the name. That shouldn't be needed,
since the cluster setting is hidden, so users would only know about it
if we tell them to enable it. Keeping "preview" in the name isn't a huge
problem, but it's just slightly annoying if we decide that we want to
keep the setting around even after the feature leaves the "preview"
status.

Also, this removes the mention of the setting in error messages. An
error should not refer to an undocumented setting, since a user would
have no way of learning more about it.

Release note: None
@rafiss rafiss force-pushed the cleanup-mr-system-db branch from d487c0f to 7ab3f77 Compare April 25, 2024 00:40
Copy link
Collaborator

@fqazi fqazi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Reviewed 2 of 4 files at r1, 3 of 3 files at r2, all commit messages.
Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @herkolategan and @renatolabs)

@rafiss
Copy link
Collaborator Author

rafiss commented May 8, 2024

tftr!

bors r+

@craig craig bot merged commit af7d2f4 into cockroachdb:master May 8, 2024
22 checks passed
@rafiss rafiss deleted the cleanup-mr-system-db branch May 9, 2024 17:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants