You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pr@cassandra.apache.org by "aviau (via GitHub)" <gi...@apache.org> on 2026/09/29 18:29:46 UTC
[PR] CASSANDRA-21595: docs: distinguish between reset_bootstrap_progress (true, false, unset) (for trunk) [cassandra]
aviau opened a new pull request, #5225:
URL: https://github.com/apache/cassandra/pull/5225
Same as https://github.com/apache/cassandra/pull/5047 but for trunk.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For additional commands, e-mail: pr-help@cassandra.apache.org
Re: [PR] CASSANDRA-21595: docs: distinguish between reset_bootstrap_progress (true, false, unset) (for trunk) [cassandra]
Posted by "ErickRamirezAU (via GitHub)" <gi...@apache.org>.
ErickRamirezAU closed pull request #5225: CASSANDRA-21595: docs: distinguish between reset_bootstrap_progress (true, false, unset) (for trunk)
URL: https://github.com/apache/cassandra/pull/5225
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For additional commands, e-mail: pr-help@cassandra.apache.org
Re: [PR] CASSANDRA-21595: docs: distinguish between reset_bootstrap_progress (true, false, unset) (for trunk) [cassandra]
Posted by "aviau (via GitHub)" <gi...@apache.org>.
aviau commented on code in PR #5225:
URL: https://github.com/apache/cassandra/pull/5225#discussion_r4191261901
##########
doc/modules/cassandra/pages/managing/operating/topo_changes.adoc:
##########
@@ -50,9 +50,31 @@ unavailable replica, set the JVM flag
On 2.2+, if the bootstrap process fails, it's possible to resume
bootstrap from the previous saved state by calling
`nodetool bootstrap resume`. If for some reason the bootstrap hangs or
-stalls, it may also be resumed by simply restarting the node. In order
-to cleanup bootstrap state and start fresh, you may set the JVM startup
-flag `-Dcassandra.reset_bootstrap_progress=true`.
+stalls, it may also be resumed by simply restarting the node.
+
+==== The `cassandra.reset_bootstrap_progress` JVM property
+
+When a bootstrap finds ranges that a previous, partially successful
+bootstrap already marked as available, the behaviour depends on the
+`cassandra.reset_bootstrap_progress` JVM startup property. Leaving it
+unset is *not* the same as setting it to `true` or to `false`.
+
+[cols=",",options="header",]
+|===
+|Value |Behaviour when previous bootstrap progress is found
+
+|unset (default) |Aborts the bootstrap with an error, so that no
Review Comment:
Sure, done!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For additional commands, e-mail: pr-help@cassandra.apache.org
Re: [PR] CASSANDRA-21595: docs: distinguish between reset_bootstrap_progress (true, false, unset) (for trunk) [cassandra]
Posted by "gandherva (via GitHub)" <gi...@apache.org>.
gandherva commented on code in PR #5225:
URL: https://github.com/apache/cassandra/pull/5225#discussion_r4191061180
##########
doc/modules/cassandra/pages/managing/operating/topo_changes.adoc:
##########
@@ -50,9 +50,31 @@ unavailable replica, set the JVM flag
On 2.2+, if the bootstrap process fails, it's possible to resume
bootstrap from the previous saved state by calling
`nodetool bootstrap resume`. If for some reason the bootstrap hangs or
-stalls, it may also be resumed by simply restarting the node. In order
-to cleanup bootstrap state and start fresh, you may set the JVM startup
-flag `-Dcassandra.reset_bootstrap_progress=true`.
+stalls, it may also be resumed by simply restarting the node.
+
+==== The `cassandra.reset_bootstrap_progress` JVM property
+
+When a bootstrap finds ranges that a previous, partially successful
+bootstrap already marked as available, the behaviour depends on the
+`cassandra.reset_bootstrap_progress` JVM startup property. Leaving it
+unset is *not* the same as setting it to `true` or to `false`.
+
+[cols=",",options="header",]
+|===
+|Value |Behaviour when previous bootstrap progress is found
+
+|unset (default) |Aborts the bootstrap with an error, so that no
Review Comment:
We could say something like this, reword as needed
"If ranges from a previous bootstrap are found, the **bootstrap usually aborts with an error**, so that no decision about the existing data is made on your behalf. If none are found, the bootstrap proceeds normally.
In some situations, the bootstrap can instead continue and reuse the ranges that were already streamed. To avoid this, we recommend setting the property to true."_
With wording like this, we are accurate by using the word usually, we also explained that in some situations there is reuse and we also recommended setting it to true.
##########
doc/modules/cassandra/pages/managing/operating/topo_changes.adoc:
##########
@@ -50,9 +50,31 @@ unavailable replica, set the JVM flag
On 2.2+, if the bootstrap process fails, it's possible to resume
bootstrap from the previous saved state by calling
`nodetool bootstrap resume`. If for some reason the bootstrap hangs or
-stalls, it may also be resumed by simply restarting the node. In order
-to cleanup bootstrap state and start fresh, you may set the JVM startup
-flag `-Dcassandra.reset_bootstrap_progress=true`.
+stalls, it may also be resumed by simply restarting the node.
+
+==== The `cassandra.reset_bootstrap_progress` JVM property
+
+When a bootstrap finds ranges that a previous, partially successful
+bootstrap already marked as available, the behaviour depends on the
+`cassandra.reset_bootstrap_progress` JVM startup property. Leaving it
+unset is *not* the same as setting it to `true` or to `false`.
+
+[cols=",",options="header",]
+|===
+|Value |Behaviour when previous bootstrap progress is found
+
+|unset (default) |Aborts the bootstrap with an error, so that no
Review Comment:
We could say something like this, reword as needed
"If ranges from a previous bootstrap are found, the **bootstrap usually aborts with an error**, so that no decision about the existing data is made on your behalf. If none are found, the bootstrap proceeds normally.
In some situations, the bootstrap can instead continue and reuse the ranges that were already streamed. To avoid this, we recommend setting the property to true."
With wording like this, we are accurate by using the word usually, we also explained that in some situations there is reuse and we also recommended setting it to true.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For additional commands, e-mail: pr-help@cassandra.apache.org
Re: [PR] CASSANDRA-21595: docs: distinguish between reset_bootstrap_progress (true, false, unset) (for trunk) [cassandra]
Posted by "gandherva (via GitHub)" <gi...@apache.org>.
gandherva commented on code in PR #5225:
URL: https://github.com/apache/cassandra/pull/5225#discussion_r4180713042
##########
doc/modules/cassandra/pages/managing/operating/topo_changes.adoc:
##########
@@ -50,9 +50,31 @@ unavailable replica, set the JVM flag
On 2.2+, if the bootstrap process fails, it's possible to resume
bootstrap from the previous saved state by calling
`nodetool bootstrap resume`. If for some reason the bootstrap hangs or
-stalls, it may also be resumed by simply restarting the node. In order
-to cleanup bootstrap state and start fresh, you may set the JVM startup
-flag `-Dcassandra.reset_bootstrap_progress=true`.
+stalls, it may also be resumed by simply restarting the node.
+
+==== The `cassandra.reset_bootstrap_progress` JVM property
+
+When a bootstrap finds ranges that a previous, partially successful
+bootstrap already marked as available, the behaviour depends on the
+`cassandra.reset_bootstrap_progress` JVM startup property. Leaving it
+unset is *not* the same as setting it to `true` or to `false`.
+
+[cols=",",options="header",]
+|===
+|Value |Behaviour when previous bootstrap progress is found
+
+|unset (default) |Aborts the bootstrap with an error, so that no
Review Comment:
Based on the current code the statement("Aborts the bootstrap with an error.." ) appears to be only true in RangeStreamer when the following condition is true
if (remaining.size() < available.full.size() + available.trans.size())
and if the condition is not true then cassandra.reset_bootstrap_progress "unset" will behave like "false". If we can capture this conditional code behavior in this statement.
-> Alternatively if we want the behvaior of unset to always given an error, the source code needs to be changed.
##########
doc/modules/cassandra/pages/managing/operating/topo_changes.adoc:
##########
@@ -50,9 +50,31 @@ unavailable replica, set the JVM flag
On 2.2+, if the bootstrap process fails, it's possible to resume
bootstrap from the previous saved state by calling
`nodetool bootstrap resume`. If for some reason the bootstrap hangs or
-stalls, it may also be resumed by simply restarting the node. In order
-to cleanup bootstrap state and start fresh, you may set the JVM startup
-flag `-Dcassandra.reset_bootstrap_progress=true`.
+stalls, it may also be resumed by simply restarting the node.
+
+==== The `cassandra.reset_bootstrap_progress` JVM property
+
+When a bootstrap finds ranges that a previous, partially successful
+bootstrap already marked as available, the behaviour depends on the
+`cassandra.reset_bootstrap_progress` JVM startup property. Leaving it
+unset is *not* the same as setting it to `true` or to `false`.
+
+[cols=",",options="header",]
+|===
+|Value |Behaviour when previous bootstrap progress is found
+
+|unset (default) |Aborts the bootstrap with an error, so that no
+decision about the existing data is made on your behalf.
+
+|`true` |Discards the recorded progress and streams all ranges again.
+The files already streamed are *not* deleted, so remove them before
+retrying or you may resurrect or duplicate data. See
+https://issues.apache.org/jira/browse/CASSANDRA-17679[CASSANDRA-17679].
+
+|`false` |Keeps the recorded progress and streams only the ranges not
+already marked as available. Only safe if the data streamed by the
Review Comment:
In Nodetool there is a comment https://github.com/apache/cassandra/blob/b15526b4816518e415aa1046d7eb98232a0c1151/test/resources/nodetool/help/bootstrap#L38
"With --force option, Use --force to resume bootstrap regardless of
--
cassandra.reset_bootstrap_progress environment variable. WARNING:
This is potentially dangerous, see CASSANDRA-17679"
I was thinking if we say "Only safe if the data streamed by the previous attempt is still intact on disk.", would we give an impression of safety as there seem to be other scenarios(listed in CASSANDRA-17679) when it is still unsafe ? so may be we can continue to call it "potentially dangerous ..." and steer readers from using 'false'.
##########
src/java/org/apache/cassandra/dht/RangeStreamer.java:
##########
@@ -729,14 +729,15 @@ public StreamResultFuture fetchAsync()
if (remaining.size() < available.full.size() + available.trans.size())
{
// If the operator hasn't specified what to do when we discover a previous partially successful bootstrap,
- // we error out and tell them to manually reconcile it. See CASSANDRA-17679.
+ // we error out and spell out the true/false choice. See CASSANDRA-17679.
if (!RESET_BOOTSTRAP_PROGRESS.isPresent())
{
List<FetchReplica> skipped = fetchReplicas.stream().filter(isAvailable).collect(Collectors.toList());
- String msg = String.format("Discovered existing bootstrap data and %s " +
- "is not configured; aborting bootstrap. Please clean up local files manually " +
- "and try again or set cassandra.reset_bootstrap_progress=true to ignore. " +
- "Found: %s. Fully available: %s. Transiently available: %s",
+ String msg = String.format("Discovered existing bootstrap data " +
Review Comment:
1. Suggestion : We could mention the field name cassandra.reset_bootstrap_progress just once(or may be twice if needed) in this error instead of mentioning it 3 times. It might make it easier to read, upto you.
2. As this error only happens when this condition is true, should we mention that in this error ? (remaining.size() < available.full.size() + available.trans.size())
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For additional commands, e-mail: pr-help@cassandra.apache.org
Re: [PR] CASSANDRA-21595: docs: distinguish between reset_bootstrap_progress (true, false, unset) (for trunk) [cassandra]
Posted by "aviau (via GitHub)" <gi...@apache.org>.
aviau commented on code in PR #5225:
URL: https://github.com/apache/cassandra/pull/5225#discussion_r4187259310
##########
src/java/org/apache/cassandra/dht/RangeStreamer.java:
##########
@@ -729,14 +729,15 @@ public StreamResultFuture fetchAsync()
if (remaining.size() < available.full.size() + available.trans.size())
{
// If the operator hasn't specified what to do when we discover a previous partially successful bootstrap,
- // we error out and tell them to manually reconcile it. See CASSANDRA-17679.
+ // we error out and spell out the true/false choice. See CASSANDRA-17679.
if (!RESET_BOOTSTRAP_PROGRESS.isPresent())
{
List<FetchReplica> skipped = fetchReplicas.stream().filter(isAvailable).collect(Collectors.toList());
- String msg = String.format("Discovered existing bootstrap data and %s " +
- "is not configured; aborting bootstrap. Please clean up local files manually " +
- "and try again or set cassandra.reset_bootstrap_progress=true to ignore. " +
- "Found: %s. Fully available: %s. Transiently available: %s",
+ String msg = String.format("Discovered existing bootstrap data " +
Review Comment:
> Suggestion : We could mention the field name cassandra.reset_bootstrap_progress just once
Agreed. The message now names cassandra.reset_bootstrap_progress once and refers to the values as 'true' and 'false' after that.
> As this error only happens when this condition is true, should we mention that in this error ? (remaining.size() < available.full.size() + available.trans.size())
The message now says the same thing in plain language: "Discovered existing bootstrap data (ranges already marked as available by a previous bootstrap attempt)"
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For additional commands, e-mail: pr-help@cassandra.apache.org
Re: [PR] CASSANDRA-21595: docs: distinguish between reset_bootstrap_progress (true, false, unset) (for trunk) [cassandra]
Posted by "aviau (via GitHub)" <gi...@apache.org>.
aviau commented on code in PR #5225:
URL: https://github.com/apache/cassandra/pull/5225#discussion_r4187227747
##########
doc/modules/cassandra/pages/managing/operating/topo_changes.adoc:
##########
@@ -50,9 +50,31 @@ unavailable replica, set the JVM flag
On 2.2+, if the bootstrap process fails, it's possible to resume
bootstrap from the previous saved state by calling
`nodetool bootstrap resume`. If for some reason the bootstrap hangs or
-stalls, it may also be resumed by simply restarting the node. In order
-to cleanup bootstrap state and start fresh, you may set the JVM startup
-flag `-Dcassandra.reset_bootstrap_progress=true`.
+stalls, it may also be resumed by simply restarting the node.
+
+==== The `cassandra.reset_bootstrap_progress` JVM property
+
+When a bootstrap finds ranges that a previous, partially successful
+bootstrap already marked as available, the behaviour depends on the
+`cassandra.reset_bootstrap_progress` JVM startup property. Leaving it
+unset is *not* the same as setting it to `true` or to `false`.
+
+[cols=",",options="header",]
+|===
+|Value |Behaviour when previous bootstrap progress is found
+
+|unset (default) |Aborts the bootstrap with an error, so that no
Review Comment:
I rewrote it like this:
> If ranges from a previous bootstrap are found, aborts the bootstrap with an error, so that no decision about the existing data is made on your behalf. If none are found, the bootstrap proceeds normally.
Not sure how you wanted to explain `if (remaining.size() < available.full.size() + available.trans.size())`, but I think my proposal is language than an operator would understand.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For additional commands, e-mail: pr-help@cassandra.apache.org
Re: [PR] CASSANDRA-21595: docs: distinguish between reset_bootstrap_progress (true, false, unset) (for trunk) [cassandra]
Posted by "gandherva (via GitHub)" <gi...@apache.org>.
gandherva commented on code in PR #5225:
URL: https://github.com/apache/cassandra/pull/5225#discussion_r4191061180
##########
doc/modules/cassandra/pages/managing/operating/topo_changes.adoc:
##########
@@ -50,9 +50,31 @@ unavailable replica, set the JVM flag
On 2.2+, if the bootstrap process fails, it's possible to resume
bootstrap from the previous saved state by calling
`nodetool bootstrap resume`. If for some reason the bootstrap hangs or
-stalls, it may also be resumed by simply restarting the node. In order
-to cleanup bootstrap state and start fresh, you may set the JVM startup
-flag `-Dcassandra.reset_bootstrap_progress=true`.
+stalls, it may also be resumed by simply restarting the node.
+
+==== The `cassandra.reset_bootstrap_progress` JVM property
+
+When a bootstrap finds ranges that a previous, partially successful
+bootstrap already marked as available, the behaviour depends on the
+`cassandra.reset_bootstrap_progress` JVM startup property. Leaving it
+unset is *not* the same as setting it to `true` or to `false`.
+
+[cols=",",options="header",]
+|===
+|Value |Behaviour when previous bootstrap progress is found
+
+|unset (default) |Aborts the bootstrap with an error, so that no
Review Comment:
We could say something like this, reword as needed
_"If ranges from a previous bootstrap are found, the **bootstrap usually aborts with an error**, so that no decision about the existing data is made on your behalf. If none are found, the bootstrap proceeds normally.
In some situations, the bootstrap can instead continue and reuse the ranges that were already streamed. To avoid this, we recommend setting the property to true."_
In this case, we are accurate by using the word usually and we also explained that in some situations there is reuse and we also recommended setting it to true.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For additional commands, e-mail: pr-help@cassandra.apache.org
Re: [PR] CASSANDRA-21595: docs: distinguish between reset_bootstrap_progress (true, false, unset) (for trunk) [cassandra]
Posted by "aviau (via GitHub)" <gi...@apache.org>.
aviau commented on code in PR #5225:
URL: https://github.com/apache/cassandra/pull/5225#discussion_r4187302027
##########
doc/modules/cassandra/pages/managing/operating/topo_changes.adoc:
##########
@@ -50,9 +50,31 @@ unavailable replica, set the JVM flag
On 2.2+, if the bootstrap process fails, it's possible to resume
bootstrap from the previous saved state by calling
`nodetool bootstrap resume`. If for some reason the bootstrap hangs or
-stalls, it may also be resumed by simply restarting the node. In order
-to cleanup bootstrap state and start fresh, you may set the JVM startup
-flag `-Dcassandra.reset_bootstrap_progress=true`.
+stalls, it may also be resumed by simply restarting the node.
+
+==== The `cassandra.reset_bootstrap_progress` JVM property
+
+When a bootstrap finds ranges that a previous, partially successful
+bootstrap already marked as available, the behaviour depends on the
+`cassandra.reset_bootstrap_progress` JVM startup property. Leaving it
+unset is *not* the same as setting it to `true` or to `false`.
+
+[cols=",",options="header",]
+|===
+|Value |Behaviour when previous bootstrap progress is found
+
+|unset (default) |Aborts the bootstrap with an error, so that no
+decision about the existing data is made on your behalf.
+
+|`true` |Discards the recorded progress and streams all ranges again.
+The files already streamed are *not* deleted, so remove them before
+retrying or you may resurrect or duplicate data. See
+https://issues.apache.org/jira/browse/CASSANDRA-17679[CASSANDRA-17679].
+
+|`false` |Keeps the recorded progress and streams only the ranges not
+already marked as available. Only safe if the data streamed by the
Review Comment:
Thanks.
I changed the false row to say "Potentially dangerous, because the data streamed by the previous attempt may be missing or incomplete". It also now says to prefer true after cleaning up the old files, and links CASSANDRA-17679. That matches the wording in the nodetool bootstrap help.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For additional commands, e-mail: pr-help@cassandra.apache.org
Re: [PR] CASSANDRA-21595: docs: distinguish between reset_bootstrap_progress (true, false, unset) (for trunk) [cassandra]
Posted by "aviau (via GitHub)" <gi...@apache.org>.
aviau commented on code in PR #5225:
URL: https://github.com/apache/cassandra/pull/5225#discussion_r4187227747
##########
doc/modules/cassandra/pages/managing/operating/topo_changes.adoc:
##########
@@ -50,9 +50,31 @@ unavailable replica, set the JVM flag
On 2.2+, if the bootstrap process fails, it's possible to resume
bootstrap from the previous saved state by calling
`nodetool bootstrap resume`. If for some reason the bootstrap hangs or
-stalls, it may also be resumed by simply restarting the node. In order
-to cleanup bootstrap state and start fresh, you may set the JVM startup
-flag `-Dcassandra.reset_bootstrap_progress=true`.
+stalls, it may also be resumed by simply restarting the node.
+
+==== The `cassandra.reset_bootstrap_progress` JVM property
+
+When a bootstrap finds ranges that a previous, partially successful
+bootstrap already marked as available, the behaviour depends on the
+`cassandra.reset_bootstrap_progress` JVM startup property. Leaving it
+unset is *not* the same as setting it to `true` or to `false`.
+
+[cols=",",options="header",]
+|===
+|Value |Behaviour when previous bootstrap progress is found
+
+|unset (default) |Aborts the bootstrap with an error, so that no
Review Comment:
I rewrote it like this:
> If ranges from a previous bootstrap are found, aborts the bootstrap with an error, so that no decision about the existing data is made on your behalf. If none are found, the bootstrap proceeds normally.
Not sure how you wanted to explain `if (remaining.size() < available.full.size() + **available.trans.size())`, but I think my proposal is language than an operator would understand.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For additional commands, e-mail: pr-help@cassandra.apache.org
Re: [PR] CASSANDRA-21595: docs: distinguish between reset_bootstrap_progress (true, false, unset) (for trunk) [cassandra]
Posted by "ErickRamirezAU (via GitHub)" <gi...@apache.org>.
ErickRamirezAU commented on PR #5225:
URL: https://github.com/apache/cassandra/pull/5225#issuecomment-6051558771
Committed via the forward merge of cassandra-6.0 into trunk as 4ab8bac4a5, with the trunk changes folded in. Closing as the commit is in. See CASSANDRA-21595. Thanks for the patch. Cheers! 🍻
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For additional commands, e-mail: pr-help@cassandra.apache.org