You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Chris Bannister (JIRA)" <ji...@apache.org> on 2018/09/08 21:16:00 UTC
[jira] [Created] (CASSANDRA-14708) protocol v5 duration wire format
is overly complex and awkward to implement for clients
Chris Bannister created CASSANDRA-14708:
-------------------------------------------
Summary: protocol v5 duration wire format is overly complex and awkward to implement for clients
Key: CASSANDRA-14708
URL: https://issues.apache.org/jira/browse/CASSANDRA-14708
Project: Cassandra
Issue Type: Bug
Reporter: Chris Bannister
Protocol V5 defines the duration type to be on the wire as months, days and nanoseconds. Days and months require a timezone to make sense of the duration and varies depending on from which they are applied for.
Go defines a [duration|https://golang.org/pkg/time/#Duration] type as nanoseconds in int64 which can represent ~290 years. Java [duration|https://docs.oracle.com/javase/8/docs/api/java/time/Duration.html] does not have way to handle months.
I suggest that before 4.0 is release the duration format is converted to just be represented as nanoseconds.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org