cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-14708) protocol v5 duration wire format is overly complex and awkward to implement for clients
Date Mon, 10 Sep 2018 11:39:00 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-14708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16609045#comment-16609045
] 

Sylvain Lebresne commented on CASSANDRA-14708:
----------------------------------------------

bq. Do you have a link to the original discussions around its inclusion

Well, it's not exactly hard to find: CASSANDRA-11873.

> 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
>            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
(v7.6.3#76005)

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


Mime
View raw message