[CASSANDRA-6147] Allow Thrift opt-in to server-side timestamps

• Type: Sub-task
• Status: Resolved
• Priority: Low
• Resolution: Won't Fix
• Fix Version/s: 2.1 beta2
• Component/s: Legacy/CQL
• Assignee: Edward Capriolo
• Reporter: Edward Capriolo

Authors

Edward Capriolo

Reviewers

Tom Hobbs

• Created: 04/Oct/13 15:27
• Updated: 16/Apr/19 09:32
• Resolved: 11/Mar/14 21:14

Description

Thrift users are still forced to generate timestamps on the client side. Currently the way the thrift bindings are generated users are forced to supply timestamps. There are two solutions I see.

• -1 as timestamp means "generate on the server side"
  This is a breaking change, for those using -1 as a timestamp (which should effectively be no one.
• Prepare yourself....
  Our thrift signatures are wrong, you can't overload methods in thrift

thrift.get(byte [], byte[], ts)

should REALLY be changed to

GetRequest g = new GetRequest()
g.setName()
g.setValue()
g.setTs() ///optional
thrift. get( g )

I know no one is going to want to make this change because thrift is quasi/dead but it would allow us to evolve thrift in a meaningful way. We could simple add these new methods under different names as well.