[jira] [Updated] (CASSANDRA-14913) Forbid re-adding static columns as regular and vice versa
[ https://issues.apache.org/jira/browse/CASSANDRA-14913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh McKenzie updated CASSANDRA-14913: -- Bug Category: Parent values: Correctness(12982)Level 1 values: Unrecoverable Corruption / Loss(13161) > Forbid re-adding static columns as regular and vice versa > - > > Key: CASSANDRA-14913 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14913 > Project: Cassandra > Issue Type: Bug > Components: Cluster/Schema >Reporter: Aleksey Yeschenko >Assignee: Aleksey Yeschenko >Priority: Normal > Fix For: 4.0 > > > Re-adding a dropped column with an incompatible kind (dropped regular > re-added as static, or dropped static re-added as regular) can ultimately > result in corruption (see CASSANDRA-14843 for more context). In 3.x, > unfortunately, we don’t persist enough context when dropping a column. In > trunk, however, we do, and it’s trivial to forbid this operation, as we > should. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14913) Forbid re-adding static columns as regular and vice versa
[ https://issues.apache.org/jira/browse/CASSANDRA-14913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-14913: - Component/s: (was: Legacy/Distributed Metadata) Cluster/Schema > Forbid re-adding static columns as regular and vice versa > - > > Key: CASSANDRA-14913 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14913 > Project: Cassandra > Issue Type: Bug > Components: Cluster/Schema >Reporter: Aleksey Yeschenko >Assignee: Aleksey Yeschenko >Priority: Major > Fix For: 4.0 > > > Re-adding a dropped column with an incompatible kind (dropped regular > re-added as static, or dropped static re-added as regular) can ultimately > result in corruption (see CASSANDRA-14843 for more context). In 3.x, > unfortunately, we don’t persist enough context when dropping a column. In > trunk, however, we do, and it’s trivial to forbid this operation, as we > should. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14913) Forbid re-adding static columns as regular and vice versa
[ https://issues.apache.org/jira/browse/CASSANDRA-14913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-14913: -- Resolution: Fixed Fix Version/s: (was: 4.0.x) 4.0 Status: Resolved (was: Patch Available) > Forbid re-adding static columns as regular and vice versa > - > > Key: CASSANDRA-14913 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14913 > Project: Cassandra > Issue Type: Bug > Components: Distributed Metadata >Reporter: Aleksey Yeschenko >Assignee: Aleksey Yeschenko >Priority: Major > Fix For: 4.0 > > > Re-adding a dropped column with an incompatible kind (dropped regular > re-added as static, or dropped static re-added as regular) can ultimately > result in corruption (see CASSANDRA-14843 for more context). In 3.x, > unfortunately, we don’t persist enough context when dropping a column. In > trunk, however, we do, and it’s trivial to forbid this operation, as we > should. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14913) Forbid re-adding static columns as regular and vice versa
[ https://issues.apache.org/jira/browse/CASSANDRA-14913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-14913: -- Status: Patch Available (was: Open) > Forbid re-adding static columns as regular and vice versa > - > > Key: CASSANDRA-14913 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14913 > Project: Cassandra > Issue Type: Bug > Components: Distributed Metadata >Reporter: Aleksey Yeschenko >Assignee: Aleksey Yeschenko >Priority: Major > Fix For: 4.0.x > > > Re-adding a dropped column with an incompatible kind (dropped regular > re-added as static, or dropped static re-added as regular) can ultimately > result in corruption (see CASSANDRA-14843 for more context). In 3.x, > unfortunately, we don’t persist enough context when dropping a column. In > trunk, however, we do, and it’s trivial to forbid this operation, as we > should. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
