[
https://issues.apache.org/jira/browse/CASSANDRA-15457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-15457:
----------------------------------------
Fix Version/s: (was: 4.x)
4.0-beta3
Since Version: 4.0-alpha1
Source Control Link:
https://github.com/apache/cassandra/commit/8b25cd58bfa646db9e6c24c51896950da02945db
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed with the string builder change
The todo is still valid - we would need to start tracking which repair session
that started the anticompaction causing the conflict, which we don't do now
> Remove bad assert when getting active compactions for an sstable
> ----------------------------------------------------------------
>
> Key: CASSANDRA-15457
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15457
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Normal
> Fix For: 4.0-beta3
>
>
> CASSANDRA-14935 added a check that an sstable can only be in a single
> 'compaction', this is wrong. An sstable can be in a validation and a normal
> compaction at the same time for example.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
