Skip to content

CASSANDRA-21595: docs: distinguish between reset_bootstrap_progress (true, false, unset) (for 6.0) - #5224

Closed
aviau wants to merge 1 commit into
apache:cassandra-6.0from
aviau:reset-bootstrap-progress-error-msg-6.0
Closed

aviau wants to merge 1 commit into
apache:cassandra-6.0from
aviau:reset-bootstrap-progress-error-msg-6.0

Conversation

@aviau

@aviau aviau commented Sep 29, 2026

Copy link
Copy Markdown
Contributor

Same as #5047 but for 6.0.

@aviau
aviau changed the base branch from trunk to cassandra-6.0 September 29, 2026 18:27
@aviau
aviau force-pushed the reset-bootstrap-progress-error-msg-6.0 branch 3 times, most recently from 319f59d to 801f0ff Compare October 1, 2026 23:40
@aviau
aviau force-pushed the reset-bootstrap-progress-error-msg-6.0 branch 4 times, most recently from 6618bc9 to 8b6ac30 Compare October 7, 2026 17:13
…trap_progress

The message did not explain that the property behaves differently when
unset, true and false, so an operator hitting the abort could not tell
which value to pick. Spell out all three behaviours in the message and
document them in topo_changes.adoc.

patch by Alexandre Viau; reviewed by TBD for CASSANDRA-21595
@aviau
aviau force-pushed the reset-bootstrap-progress-error-msg-6.0 branch from 8b6ac30 to c24cfcf Compare October 7, 2026 17:15

@ErickRamirezAU ErickRamirezAU left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

+1 thanks for applying the suggested edits. I'll resolve the merge conflict for CHANGES.txt myself. 🍻

@ErickRamirezAU

Copy link
Copy Markdown
Contributor

Committed via the forward merge of cassandra-5.0 into cassandra-6.0 as 05fecbc, with the 6.0 changes folded in. Closing as the commit is in. See CASSANDRA-21595. Thanks for the patch. Cheers! 🍻

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