[CASSANDRA-8246] Default timestamp for QueryOptions should be Long.MIN_VALUE

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.1.2
• Component/s: Legacy/CQL
• Severity: Normal
• Since Version: 2.1.2
• Assignee: Sam Tunnicliffe
• Reporter: Sam Tunnicliffe

Authors

Sam Tunnicliffe

Reviewers

Sylvain Lebresne

• Created: 03/Nov/14 19:01
• Updated: 16/Apr/19 09:31
• Resolved: 04/Nov/14 08:48

Description

CASSANDRA-8139 adds proper handling for negative timestamps, but one case was missed in the merge to cassandra-2.1.
QueryOptions.SpecificOptions.DEFAULT is still created with a timestamp of -1, so statements which do not come in via the native protocol will retain this timestamp and not be assigned a server-side timestamp at execution time.QueryOptions.Codec does the right thing, so statements that do come via the protocol are unaffected.