You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Tellier Benoit (JIRA)" <se...@james.apache.org> on 2018/01/29 10:55:00 UTC

[jira] [Comment Edited] (JAMES-1729) Cassandra Codec for ZonedDateTime

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

Tellier Benoit edited comment on JAMES-1729 at 1/29/18 10:54 AM:
-----------------------------------------------------------------

That is a mistake, I guess I missed the CODEC part. But we do have a custom type. I will re-open.


was (Author: btellier):
That is a mistake, I guess I missed the CODEC part. I will re-open.

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

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