[CASSANDRA-15303] drop column statement should not initialize timestamp because of statement cache

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-alpha4, 4.0
• Component/s: CQL/Interpreter
• Bug Category: Correctness
• Severity: Normal
• Complexity: Normal
• Discovered By: Unit Test
• Platform: All
• Since Version: 4.0

Source Control Link

https://github.com/apache/cassandra/commit/722d10b2c5999f19f3a912dc2fbaeb71cef65a07

Test and Documentation Plan

Verified by unit test

• Assignee: Zhao Yang
• Reporter: Zhao Yang

Authors

Zhao Yang

Reviewers

Benjamin Lerer

• Created: 06/Sep/19 03:23
• Updated: 15/May/20 08:41
• Resolved: 16/Mar/20 15:21

Description

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