[
https://issues.apache.org/jira/browse/CASSANDRA-15303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17063506#comment-17063506
]
Alex Petrov commented on CASSANDRA-15303:
-----------------------------------------
This commit has broken AlterTest. I've ninja-commited the fix for trunk here
[b29af2925cddacb4ab8b429b31917748781fbe5d|https://github.com/apache/cassandra/commit/b29af2925cddacb4ab8b429b31917748781fbe5d]
> 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.0
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
