[jira] [Commented] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909987#comment-17909987 ] Ke Han commented on CASSANDRA-18956: Hi [Stefan Miklosovic|https://issues.apach

[jira] [Updated] (CASSANDRA-18108) Data loss after a system restart of 3.11.17/4.1.4

[ https://issues.apache.org/jira/browse/CASSANDRA-18108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18108: --- Summary: Data loss after a system restart of 3.11.17/4.1.4 (was: Data loss after a system resta

[jira] [Updated] (CASSANDRA-18108) Data loss after a system restart/upgrade (3.11.17)

[ https://issues.apache.org/jira/browse/CASSANDRA-18108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18108: --- Description: When we upgrade Cassandra from 3.11.17 to 4.0.12, we found a data loss during the

[jira] [Updated] (CASSANDRA-18108) Data loss after a system restart/upgrade (3.11.17)

[ https://issues.apache.org/jira/browse/CASSANDRA-18108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18108: --- Description: When we upgrade Cassandra from 3.11.17 to 4.0.12, we found a data loss during the

[jira] [Commented] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783403#comment-17783403 ] Ke Han commented on CASSANDRA-18956: [~smiklosovic] Of course. Thanks for the he

[jira] [Comment Edited] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783296#comment-17783296 ] Ke Han edited comment on CASSANDRA-18956 at 11/6/23 5:25 PM: -

[jira] [Comment Edited] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783296#comment-17783296 ] Ke Han edited comment on CASSANDRA-18956 at 11/6/23 5:25 PM: -

[jira] [Commented] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783296#comment-17783296 ] Ke Han commented on CASSANDRA-18956: During my local testing, I noticed that whe

[jira] [Comment Edited] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783296#comment-17783296 ] Ke Han edited comment on CASSANDRA-18956 at 11/6/23 5:24 PM: -

[jira] [Commented] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783270#comment-17783270 ] Ke Han commented on CASSANDRA-18956: [~smiklosovic] Regression fixed. Could you

[jira] [Commented] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783058#comment-17783058 ] Ke Han commented on CASSANDRA-18956: Hi [~smiklosovic], I have fixed it by (1) e

[jira] [Commented] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783056#comment-17783056 ] Ke Han commented on CASSANDRA-18956: [~smiklosovic] Definitely. The suggestions

[jira] [Commented] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783022#comment-17783022 ] Ke Han commented on CASSANDRA-18956: [~mikloso...@pm.me] Thanks for the suggesti

[jira] [Commented] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17782939#comment-17782939 ] Ke Han commented on CASSANDRA-18956: Hi [~smiklosovic] I have fixed the unit tes

[jira] [Comment Edited] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17782939#comment-17782939 ] Ke Han edited comment on CASSANDRA-18956 at 11/5/23 12:35 AM:

[jira] [Commented] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17782633#comment-17782633 ] Ke Han commented on CASSANDRA-18956: [~smiklosovic] Thanks for the information!

[jira] [Commented] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17782588#comment-17782588 ] Ke Han commented on CASSANDRA-18956: [Stefan Miklosovic|https://issues.apache.o

[jira] [Updated] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18956: --- Description: After migrating data from 2.1.22 (released 2022-06-17) to 3.0.29 (released 2023-05

[jira] [Updated] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18956: --- Description: After migrating data from 2.1.22 (released 2022-06-17) to 3.0.29 (released 2023-05

[jira] [Assigned] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han reassigned CASSANDRA-18956: -- Assignee: Ke Han > Metadata Loss caused by unchecked rename column when upgrading from 2.

[jira] [Comment Edited] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780581#comment-17780581 ] Ke Han edited comment on CASSANDRA-18956 at 10/28/23 2:30 AM:

[jira] [Commented] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780581#comment-17780581 ] Ke Han commented on CASSANDRA-18956: [~mikloso...@pm.me] I have added a unit tes

[jira] [Commented] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779968#comment-17779968 ] Ke Han commented on CASSANDRA-18956: [~mikloso...@pm.me] Absolutely, let me give

[jira] [Comment Edited] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779291#comment-17779291 ] Ke Han edited comment on CASSANDRA-18956 at 10/26/23 3:30 AM:

[jira] [Commented] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779553#comment-17779553 ] Ke Han commented on CASSANDRA-18956: [~mikloso...@pm.me] No. It only exists in 3

[jira] [Comment Edited] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779291#comment-17779291 ] Ke Han edited comment on CASSANDRA-18956 at 10/25/23 1:38 AM:

[jira] [Commented] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779291#comment-17779291 ] Ke Han commented on CASSANDRA-18956: [~smiklosovic] Thanks for the reply! (1) T

[jira] [Updated] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18956: --- Description: After migrating data from 2.1.22 (released 2022-06-17) to 3.0.29 (released 2023-05

[jira] [Updated] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18956: --- Summary: Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29 (was

[jira] [Updated] (CASSANDRA-18956) Metadata Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

[ https://issues.apache.org/jira/browse/CASSANDRA-18956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18956: --- Description: After migrating data from 2.1.22 (released 2022-06-17) to 3.0.29 (released 2023-05

[jira] [Created] (CASSANDRA-18956) Data Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29

Ke Han created CASSANDRA-18956: -- Summary: Data Loss caused by unchecked rename column when upgrading from 2.x to 3.0.29 Key: CASSANDRA-18956 URL: https://issues.apache.org/jira/browse/CASSANDRA-18956 Pro

[jira] [Comment Edited] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.16 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17772660#comment-17772660 ] Ke Han edited comment on CASSANDRA-18728 at 10/6/23 6:19 PM: -

[jira] [Commented] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.16 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17772660#comment-17772660 ] Ke Han commented on CASSANDRA-18728: [~brandon.williams] Hi Brandon, I have iden

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.16 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Test and Documentation Plan: (was: [https://github.com/apache/cassandra/pull/2731/files]  )

[jira] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.16 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728 ] Ke Han deleted comment on CASSANDRA-18728: was (Author: JIRAUSER289562): (Update) Thanks! I have found the way. It can be constructed using cassandra-cli. Using cqlsh seems not able to r

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.16 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Test and Documentation Plan: [https://github.com/apache/cassandra/pull/2731/files]  

[jira] [Assigned] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.16 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han reassigned CASSANDRA-18728: -- Assignee: Ke Han > [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifie

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.16 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Description: h1. Bug Description When using Cassandra 3.11.16 to load legacy data from 2.2.10,

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.16 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Description: h1. Bug Description When using Cassandra 3.11.16 to load legacy data from 2.2.10,

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.16 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Description:   h1. Bug Description When using Cassandra 3.11.16 to load legacy data from 2.2.10

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.16 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Description: h1. Bug Description When using Cassandra 3.11.16 to load legacy data from 2.2.10,

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.16 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Description: h1. Bug Description When using Cassandra 3.11.16 to load legacy data from 2.2.10,

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.16 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Description: h1. Bug Description When using Cassandra 3.11.16 to load legacy data from 2.2.10,

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.16 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Description: h1. Bug Description When using Cassandra 3.11.16 to load legacy data from 2.2.10,

[jira] [Comment Edited] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.16 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17771359#comment-17771359 ] Ke Han edited comment on CASSANDRA-18728 at 10/4/23 8:52 PM: -

[jira] [Comment Edited] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.16 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17771359#comment-17771359 ] Ke Han edited comment on CASSANDRA-18728 at 10/3/23 7:29 AM: -

[jira] [Commented] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.16 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17771359#comment-17771359 ] Ke Han commented on CASSANDRA-18728: [~wadey] Hi Wade, is there any chance you c

[jira] [Comment Edited] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.16 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17771359#comment-17771359 ] Ke Han edited comment on CASSANDRA-18728 at 10/3/23 7:28 AM: -

[jira] [Updated] (CASSANDRA-18897) NPE in getHostId when fresh starting up the 3.11.16 cluster

[ https://issues.apache.org/jira/browse/CASSANDRA-18897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18897: --- Description: When I start up cassandra 3.11.16 cluster (Fresh Start, 3 nodes), I noticed the fo

[jira] [Updated] (CASSANDRA-18897) NPE in getHostId when fresh starting up the 3.11.16 cluster

[ https://issues.apache.org/jira/browse/CASSANDRA-18897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18897: --- Description: When I start up cassandra 3.11.16 cluster (Fresh Start, 3 nodes), I noticed the fo

[jira] [Created] (CASSANDRA-18897) NPE in getHostId when fresh starting up the 3.11.16 cluster

Ke Han created CASSANDRA-18897: -- Summary: NPE in getHostId when fresh starting up the 3.11.16 cluster Key: CASSANDRA-18897 URL: https://issues.apache.org/jira/browse/CASSANDRA-18897 Project: Cassandra

[jira] [Commented] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.16 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17769272#comment-17769272 ] Ke Han commented on CASSANDRA-18728: I have found the root cause and got an init

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.16 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Summary: [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.16 l

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.15 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Description: h1. Bug Description When using Cassandra 3.11.15 to load legacy data from 2.2.10,

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.15 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Description: h1. Bug Description When using Cassandra 3.11.16 to load legacy data from 2.2.10,

[jira] [Commented] (CASSANDRA-18858) AssertionError: Unknown keyspace after dropping a keyspace combined with drain operation

[ https://issues.apache.org/jira/browse/CASSANDRA-18858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17765978#comment-17765978 ] Ke Han commented on CASSANDRA-18858: [~brandon.williams] Make sense. Thanks! >

[jira] [Commented] (CASSANDRA-18858) AssertionError: Unknown keyspace after dropping a keyspace combined with drain operation

[ https://issues.apache.org/jira/browse/CASSANDRA-18858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17765961#comment-17765961 ] Ke Han commented on CASSANDRA-18858: [~brandon.williams] Thanks for the reply! Y

[jira] [Updated] (CASSANDRA-18858) AssertionError: Unknown keyspace after dropping a keyspace combined with drain operation

[ https://issues.apache.org/jira/browse/CASSANDRA-18858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18858: --- Description: After dropping the keyspace and then perform the drain, I met the following ERROR

[jira] [Updated] (CASSANDRA-18858) AssertionError: Unknown keyspace after dropping a keyspace combined with drain operation

[ https://issues.apache.org/jira/browse/CASSANDRA-18858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18858: --- Description: After dropping the keyspace and then perform the drain, I met the following ERROR

[jira] [Updated] (CASSANDRA-18858) AssertionError: Unknown keyspace after dropping a keyspace combined with drain operation

[ https://issues.apache.org/jira/browse/CASSANDRA-18858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18858: --- Description: After dropping the keyspace and then perform the drain, I met the following ERROR

[jira] [Commented] (CASSANDRA-18636) AssertionError: Unknown keyspace after dropping a keyspace

[ https://issues.apache.org/jira/browse/CASSANDRA-18636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17765898#comment-17765898 ] Ke Han commented on CASSANDRA-18636: Hi [~smiklosovic], I found another possible

[jira] [Updated] (CASSANDRA-18858) AssertionError: Unknown keyspace after dropping a keyspace combined with drain operation

[ https://issues.apache.org/jira/browse/CASSANDRA-18858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18858: --- Description: After dropping the keyspace and then perform the drain, I met the following ERROR

[jira] [Updated] (CASSANDRA-18858) AssertionError: Unknown keyspace after dropping a keyspace combined with drain operation

[ https://issues.apache.org/jira/browse/CASSANDRA-18858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18858: --- Description: After dropping the keyspace and then perform the drain, I met the following ERROR

[jira] [Created] (CASSANDRA-18858) AssertionError: Unknown keyspace after dropping a keyspace combined with drain operation

Ke Han created CASSANDRA-18858: -- Summary: AssertionError: Unknown keyspace after dropping a keyspace combined with drain operation Key: CASSANDRA-18858 URL: https://issues.apache.org/jira/browse/CASSANDRA-18858

[jira] [Commented] (CASSANDRA-18843) Query parsing error handling problem: NPE when user types an incorrect query statement

[ https://issues.apache.org/jira/browse/CASSANDRA-18843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17764742#comment-17764742 ] Ke Han commented on CASSANDRA-18843: [~maxwellguo] It's an incorrect user input

[jira] [Created] (CASSANDRA-18846) CancellationException when shutting down the 3.11.16 node

Ke Han created CASSANDRA-18846: -- Summary: CancellationException when shutting down the 3.11.16 node Key: CASSANDRA-18846 URL: https://issues.apache.org/jira/browse/CASSANDRA-18846 Project: Cassandra

[jira] [Updated] (CASSANDRA-18843) Query parsing error handling problem: NPE when user types an incorrect query statement

[ https://issues.apache.org/jira/browse/CASSANDRA-18843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18843: --- Description: When using cassandra cqlsh shell (4.1.3 or 3.11.16), typing the following query wi

[jira] [Updated] (CASSANDRA-18644) ERROR: ArrayIndexOutOfBoundsException: -1 in MigrationStage thread when shutdown Cassandra-3.11.16 node

[ https://issues.apache.org/jira/browse/CASSANDRA-18644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18644: --- Summary: ERROR: ArrayIndexOutOfBoundsException: -1 in MigrationStage thread when shutdown Cassan

[jira] [Updated] (CASSANDRA-18644) ERROR: ArrayIndexOutOfBoundsException: -1 in MigrationStage thread when shutdown Cassandra-3.11.16 node

[ https://issues.apache.org/jira/browse/CASSANDRA-18644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18644: --- Description: h2. Symptoms I was migrating from Cassandra-3.11.15 to Cassandra-4.1.2(Single node

[jira] [Assigned] (CASSANDRA-18091) Column update lost after a full stop upgrade from 4.0.7 to 4.1.0

[ https://issues.apache.org/jira/browse/CASSANDRA-18091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han reassigned CASSANDRA-18091: -- Assignee: Ke Han > Column update lost after a full stop upgrade from 4.0.7 to 4.1.0 > ---

[jira] [Updated] (CASSANDRA-18843) Query parsing error handling problem: NPE when user types an incorrect query statement

[ https://issues.apache.org/jira/browse/CASSANDRA-18843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18843: --- Description: When using cassandra cqlsh shell (4.1.3 or 3.11.16), typing the following query wi

[jira] [Created] (CASSANDRA-18843) Query parsing error handling problem: NPE when user types an incorrect query statement

Ke Han created CASSANDRA-18843: -- Summary: Query parsing error handling problem: NPE when user types an incorrect query statement Key: CASSANDRA-18843 URL: https://issues.apache.org/jira/browse/CASSANDRA-18843

[jira] [Updated] (CASSANDRA-18091) Column update lost after a full stop upgrade from 4.0.7 to 4.1.0

[ https://issues.apache.org/jira/browse/CASSANDRA-18091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18091: --- Resolution: Not A Problem Status: Resolved (was: Triage Needed) Consistency level is no

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.15 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Description: h1. Bug Description When using Cassandra 3.11.15 to load legacy data from 2.2.10,

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.15 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Bug Category: Parent values: Correctness(12982) > [Transient Bug] Incorrect ByteBuffer represent

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.15 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Description: h1. Bug Description When using Cassandra 3.11.15 to load legacy data from 2.2.10,

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.15 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Description: h1. Bug Description When using Cassandra 3.11.15 to load legacy data from 2.2.10,

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.15 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Description: h1. Bug Description When using Cassandra 3.11.15 to load legacy data from 2.2.10,

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.15 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Description: When using Cassandra 3.11.15 to load legacy data from 2.2.10, I noticed that the b

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.15 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Description: h1. Description When using Cassandra 3.11.15 to load legacy data from 2.2.10, I no

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.15 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Description: h1. Description When using Cassandra 3.11.15 to load legacy data from 2.2.10, I no

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.15 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Description: h1. Description When using Cassandra 3.11.15 to load legacy data from 2.2.10, I no

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.15 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Description: h1. Description When using Cassandra 3.11.15 to load legacy data from 2.2.10, I no

[jira] [Updated] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.15 loading legacy data from 2.x

[ https://issues.apache.org/jira/browse/CASSANDRA-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18728: --- Description: h1. Description When using Cassandra 3.11.15 to load legacy data from 2.2.10, I no

[jira] [Created] (CASSANDRA-18728) [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.15 loading legacy data from 2.x

Ke Han created CASSANDRA-18728: -- Summary: [Transient Bug] Incorrect ByteBuffer representation of ColumnIdentifiers when 3.11.15 loading legacy data from 2.x Key: CASSANDRA-18728 URL: https://issues.apache.org/jira/br

[jira] [Updated] (CASSANDRA-18644) ERROR: ArrayIndexOutOfBoundsException: -1 in MigrationStage thread when shutdown Cassandra-3.11.15 node

[ https://issues.apache.org/jira/browse/CASSANDRA-18644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18644: --- Description: h2. Symptoms I was migrating from Cassandra-3.11.15 to Cassandra-4.1.2(Single node

[jira] [Created] (CASSANDRA-18644) ERROR: ArrayIndexOutOfBoundsException: -1 in MigrationStage thread when shutdown Cassandra-3.11.15 node

Ke Han created CASSANDRA-18644: -- Summary: ERROR: ArrayIndexOutOfBoundsException: -1 in MigrationStage thread when shutdown Cassandra-3.11.15 node Key: CASSANDRA-18644 URL: https://issues.apache.org/jira/browse/CASSAN

[jira] [Updated] (CASSANDRA-18638) ERROR: Invalid consistency level: NODE_LOCAL when using partition denylist in 4.1.2

[ https://issues.apache.org/jira/browse/CASSANDRA-18638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18638: --- Description: When I was testing the upgrade from Cassandra-3.11.15 to Cassandra-4.1.2 (single n

[jira] [Created] (CASSANDRA-18638) ERROR: Invalid consistency level: NODE_LOCAL when using partition denylist in 4.1.2

Ke Han created CASSANDRA-18638: -- Summary: ERROR: Invalid consistency level: NODE_LOCAL when using partition denylist in 4.1.2 Key: CASSANDRA-18638 URL: https://issues.apache.org/jira/browse/CASSANDRA-18638

[jira] [Updated] (CASSANDRA-18636) AssertionError: Unknown keyspace after dropping a keyspace

[ https://issues.apache.org/jira/browse/CASSANDRA-18636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18636: --- Description: When running Cassandra cluster (3 nodes) in 3.11.15, I noticed that there is an ER

[jira] [Updated] (CASSANDRA-18636) AssertionError: Unknown keyspace after dropping a keyspace

[ https://issues.apache.org/jira/browse/CASSANDRA-18636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18636: --- Description: When running Cassandra cluster (3 nodes) in 3.11.15, I noticed that there is an ER

[jira] [Updated] (CASSANDRA-18636) AssertionError: Unknown keyspace after dropping a keyspace

[ https://issues.apache.org/jira/browse/CASSANDRA-18636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18636: --- Description: When running Cassandra cluster (3 nodes) in 3.11.15, I noticed that there is an ER

[jira] [Updated] (CASSANDRA-18636) AssertionError: Unknown keyspace after dropping a keyspace

[ https://issues.apache.org/jira/browse/CASSANDRA-18636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18636: --- Attachment: system.log > AssertionError: Unknown keyspace after dropping a keyspace > --

[jira] [Updated] (CASSANDRA-18636) AssertionError: Unknown keyspace after dropping a keyspace

[ https://issues.apache.org/jira/browse/CASSANDRA-18636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18636: --- Description: When running Cassandra cluster (3 nodes) in 3.11.15, I noticed that there is an ER

[jira] [Updated] (CASSANDRA-18636) AssertionError: Unknown keyspace after dropping a keyspace

[ https://issues.apache.org/jira/browse/CASSANDRA-18636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18636: --- Description: When running Cassandra cluster (3 nodes) in 3.11.15, I noticed that there is an ER

[jira] [Updated] (CASSANDRA-18636) AssertionError: Unknown keyspace after dropping a keyspace

[ https://issues.apache.org/jira/browse/CASSANDRA-18636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18636: --- Description: When running Cassandra cluster (3 nodes) in 3.11.15, I noticed that there is an ER

[jira] [Updated] (CASSANDRA-18636) AssertionError: Unknown keyspace after dropping a keyspace

[ https://issues.apache.org/jira/browse/CASSANDRA-18636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ke Han updated CASSANDRA-18636: --- Description: When running Cassandra cluster (3 nodes) in 3.11.15, I noticed that there is an ER

[jira] [Created] (CASSANDRA-18636) AssertionError: Unknown keyspace after dropping a keyspace

Ke Han created CASSANDRA-18636: -- Summary: AssertionError: Unknown keyspace after dropping a keyspace Key: CASSANDRA-18636 URL: https://issues.apache.org/jira/browse/CASSANDRA-18636 Project: Cassandra

[jira] [Commented] (CASSANDRA-18628) Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15

[ https://issues.apache.org/jira/browse/CASSANDRA-18628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737358#comment-17737358 ] Ke Han commented on CASSANDRA-18628: It works, thanks a lot! It seems it's case

[jira] [Comment Edited] (CASSANDRA-18628) Handle special column name when upgrading from 2.2.19 to 3.0.29/3.11.15

[ https://issues.apache.org/jira/browse/CASSANDRA-18628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737356#comment-17737356 ] Ke Han edited comment on CASSANDRA-18628 at 6/26/23 9:50 PM: -

  1   2   >