[
https://issues.apache.org/jira/browse/CASSANDRA-21527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-21527:
----------------------------------------
Fix Version/s: 4.0.22
4.1.13
5.0.10
6.0-alpha3
(was: 4.0.x)
(was: 4.1.x)
(was: 5.0.x)
(was: 6.x)
Since Version: 4.0.0
Source Control Link:
https://github.com/apache/cassandra/commit/7b4170491d124cd817278e01f0ff3f09012db889
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed. Thanks for the patch and review!
> 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.22, 4.1.13, 5.0.10, 6.0-alpha3, 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: 3h 10m
> 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]
