[ https://issues.apache.org/jira/browse/CASSANDRA-15303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060130#comment-17060130 ]
Benjamin Lerer commented on CASSANDRA-15303: -------------------------------------------- The fix looks good. I just believe that we should fix the {{AlterTest}} test to not use prepared statements for schema changes by default. I pushed a patch for that [here|https://github.com/apache/cassandra/commit/56c1b0538e344f030cec622f05b9bb220d93ef9f]. [~jasonstack] If my change looks good to you, I think we should push it at the same time as your fix. > drop column statement should not initialize timestamp because of statement > cache > -------------------------------------------------------------------------------- > > Key: CASSANDRA-15303 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15303 > Project: Cassandra > Issue Type: Bug > Components: CQL/Interpreter > Reporter: ZhaoYang > Assignee: ZhaoYang > Priority: Normal > Fix For: 4.x > > > When executing drop-column query without timestamp, > {{AlterTableStatement#Raw}} initializes a default timestamp and then the > prepared statement is cached. The same timestamp will be reused for the same > drop-column query. (related to CASSANDRA-13426) > > The fix is to use NULL timestamp to indicate: using statement execution time > instead. > > patch: > [https://github.com/jasonstack/cassandra/commits/fix-drop-column-timestamp] -- 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