james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raphaël Ouazana (JIRA) <server-...@james.apache.org>
Subject [jira] [Commented] (JAMES-1729) Cassandra Codec for ZonedDateTime
Date Thu, 03 May 2018 09:40:00 GMT

    [ https://issues.apache.org/jira/browse/JAMES-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462193#comment-16462193

Raphaël Ouazana commented on JAMES-1729:

It seems to have been fixed in Cassandra Driver: https://github.com/datastax/java-driver/commit/c20f24bf4a80fd121819df19047d22f6dcd8185f#diff-4cf3a92ffd4707d49891a73e648c04db
So we may want to use it now.

> Cassandra Codec for ZonedDateTime
> ---------------------------------
>                 Key: JAMES-1729
>                 URL: https://issues.apache.org/jira/browse/JAMES-1729
>             Project: James Server
>          Issue Type: Improvement
>          Components: cassandra
>            Reporter: Tellier Benoit
>            Priority: Major
> We should write our own codec for ZonedDateTime, waiting for official codec to persist
timezones, and not just offsets.
> Due to initialization conditions, it is much easier to write the codec using User Defined
Types than with TupleTypes.
> Also, we should pay attention to persist the whole timeZone
> Acceptance criteria :
>  - Should allow to retrieve ZonedDateTime as stored
>  - Zoned Date Time persisted in James should use it.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message