docs: move graceful cluster reconfiguration availability from v26.34 to v26.35 - #37894
Merged
Merged
Conversation
maheshwarip
marked this pull request as ready for review
July 27, 2026 16:10
maheshwarip
enabled auto-merge (squash)
July 27, 2026 16:10
maheshwarip
approved these changes
Jul 27, 2026
maheshwarip
added a commit
that referenced
this pull request
Jul 31, 2026
…chema guide Announce Graceful Cluster Reconfiguration (async ALTER CLUSTER) in v26.35, restoring the draft text removed from v26.34 in #37894, and also in v26.34.1 with a Self-Managed only marker (matching the docs/v26.34.1-graceful-cluster-reconfiguration branch). Move the AWS Glue Schema Registry sinks note from v26.34 to v26.35 and drop the Cloud-only marker, since the feature now ships on Self-Managed too. Add a v26.35 feature note linking the new guide on handling upstream Avro schema changes for Kafka sources. The guide file itself is synced verbatim from main, as is the v26.34.1 section, since this branch was cut before they landed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Requested by Pranshu Maheshwari · Slack thread
Motivation
Graceful cluster reconfiguration (asynchronous
ALTER CLUSTERsize changes that resize without downtime) will not ship in v26.34 as the docs currently state. Its availability is moving to v26.35. This corrects the docs so readers are pointed at the right version and so v26.34 doesn't advertise a feature it doesn't have.Description
Before / After (what a docs reader sees):
ALTER CLUSTERreference: Previously "Downtime considerations for v26.34 or after" / "Starting in v26.34, ... resizes gracefully" and a paired "Downtime considerations for v26.33 or before". Now the boundary reads "v26.35 or after" / "Starting in v26.35, ..." with the paired heading bumped to "v26.34 or before" so no version falls between the two sections.CREATE CLUSTERreference: Previously "As of v26.34, resizing is graceful ..." and "In versions before v26.34, resizing could incur downtime ...". Now both halves read v26.35.How:
doc/user/content/releases/_index.md— removed only the "Graceful Cluster Reconfiguration" section from v26.34 (heading + body). Other v26.34 notes are untouched.doc/user/content/sql/alter-cluster.md— bumped the paired section-heading boundary from 26.34/26.33 to 26.35/26.34, and the "Starting in v26.34" body text to v26.35.doc/user/content/sql/create-cluster.md— bumped both halves of the before/after statement to v26.35.No shortcode or headless-include content described this behavior, so all changes live in these three markdown files.
Verification
v26.34graceful-reconfiguration references remain in the two cluster reference docs and that the release note was removed.doc/user/; the still-referenced#resizing-processand#monitoring-a-resizeanchors are unchanged sub-headings.doc/userwith the pinned extended Hugo (v0.152.2) viahugo --quiet: build succeeded with no errors or warnings.