[
https://issues.apache.org/jira/browse/CASSANDRA-21527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18104952#comment-18104952
]
Caleb Rackliffe commented on CASSANDRA-21527:
---------------------------------------------
The 5.0 CI run is quite clean, with the exception of a few broken pipes in
Python upgrade dtests that are almost certainly not related to this patch. At
this point, I'd say that this is ready to commit. I'll do that Monday unless
[~smiklosovic] beats me to it.
> truncateBlocking silently succeeds when runWithCompactionsDisabled returns
> null
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-21527
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21527
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Legacy/Core
> Reporter: Nivy Kani
> Assignee: Nivy Kani
> Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 6.x, 7.x
>
> Attachments: 6.0-ci_summary.html, 6.0-result_details.tar.gz,
> ci_summary-1.html, ci_summary-2.html, ci_summary-3.html, ci_summary.html,
> result_details.tar-1.gz, result_details.tar-2.gz, result_details.tar.gz
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> Currently, runWithCompactionsDisabled can’t tell the difference between a
> successful truncate vs a truncate that wasn’t successful due to being unable
> to stop compaction, because both return null. In either case, it logs
> “Truncate is complete” and returns success to the user.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]