You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "ZhaoYang (Jira)" <ji...@apache.org> on 2019/09/06 03:24:00 UTC

[jira] [Created] (CASSANDRA-15303) drop column statement should not initialize timestamp because of statement cache

ZhaoYang created CASSANDRA-15303:
------------------------------------

             Summary: 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


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 to indicate: using statement execution time instead.

 

patch: [https://github.com/jasonstack/cassandra/tree/fix-drop-column-timestamp]



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org