[jira] [Updated] (CASSANDRA-14948) Backport dropped column checks to 3.11

[ https://issues.apache.org/jira/browse/CASSANDRA-14948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-14948: -- Fix Version/s: 3.11.x Status: Patch Available (was: Open) > Backport

[jira] [Created] (CASSANDRA-14948) Backport dropped column checks to 3.11

Vincent White created CASSANDRA-14948: - Summary: Backport dropped column checks to 3.11 Key: CASSANDRA-14948 URL: https://issues.apache.org/jira/browse/CASSANDRA-14948 Project: Cassandra

[jira] [Updated] (CASSANDRA-14564) issue while adding a column in a table with compact storage

[ https://issues.apache.org/jira/browse/CASSANDRA-14564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent White updated CASSANDRA-14564: -- Assignee: Vincent White Fix Version/s: 3.11.x Status: Patch

[jira] [Commented] (CASSANDRA-14564) issue while adding a column in a table with compact storage

[ https://issues.apache.org/jira/browse/CASSANDRA-14564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732694#comment-16732694 ] Vincent White commented on CASSANDRA-14564: --- Looks like the behaviour your seeing is

[jira] [Commented] (CASSANDRA-14526) dtest to validate Cassandra state post failed/successful bootstrap

[ https://issues.apache.org/jira/browse/CASSANDRA-14526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732692#comment-16732692 ] Jay Zhuang commented on CASSANDRA-14526: I still see the same failure after updating the

[jira] [Created] (CASSANDRA-14947) in the tarball download of cassandra 3.11.3 there is an issue redirecting system.log and debug.log via $cassandra.logdir

simon created CASSANDRA-14947: - Summary: in the tarball download of cassandra 3.11.3 there is an issue redirecting system.log and debug.log via $cassandra.logdir Key: CASSANDRA-14947 URL:

[jira] [Commented] (CASSANDRA-14526) dtest to validate Cassandra state post failed/successful bootstrap

[ https://issues.apache.org/jira/browse/CASSANDRA-14526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732588#comment-16732588 ] Jaydeepkumar Chovatia commented on CASSANDRA-14526: --- It is already fixed as part

[jira] [Assigned] (CASSANDRA-14932) removenode coordinator, and its hints data will be lost

[ https://issues.apache.org/jira/browse/CASSANDRA-14932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ariel Weisberg reassigned CASSANDRA-14932: -- Assignee: Ariel Weisberg (was: sunhaihong) > removenode coordinator,

[jira] [Commented] (CASSANDRA-14895) SSTable loader exception when loading 3.0/3.11 compact tables into 4.0

[ https://issues.apache.org/jira/browse/CASSANDRA-14895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732296#comment-16732296 ] Ariel Weisberg commented on CASSANDRA-14895: So it doesn't get lost this is a test bug

[jira] [Resolved] (CASSANDRA-14932) removenode coordinator, and its hints data will be lost

[ https://issues.apache.org/jira/browse/CASSANDRA-14932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ariel Weisberg resolved CASSANDRA-14932. Resolution: Not A Problem This is the expected behavior for ANY. You don't

[jira] [Updated] (CASSANDRA-14928) MigrationManager attempts to pull schema from different major version nodes

[ https://issues.apache.org/jira/browse/CASSANDRA-14928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-14928: - Component/s: (was: 4.0) > MigrationManager attempts to pull schema from different major