C. Scott Andreas updated CASSANDRA-14708:
    Component/s: CQL

> 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
>          Components: CQL
>            Reporter: Chris Bannister
>            Priority: Major
> 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

To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to