You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Ji Liu (JIRA)" <ji...@apache.org> on 2019/07/17 11:38:00 UTC

[jira] [Updated] (ARROW-5967) [Java] DateUtility#timeZoneList is not correct

     [ https://issues.apache.org/jira/browse/ARROW-5967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji Liu updated ARROW-5967:
--------------------------
    Component/s: Java

> [Java] DateUtility#timeZoneList is not correct
> ----------------------------------------------
>
>                 Key: ARROW-5967
>                 URL: https://issues.apache.org/jira/browse/ARROW-5967
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Java
>            Reporter: Ji Liu
>            Assignee: Ji Liu
>            Priority: Minor
>
> Now {{timeZoneList}} in {{DateUtility}} belongs to Joda time.
> Since we have replace Joda time with Java time in ARROW-2015, this should also be changed.
> {{TimeStampXXTZVectors}} have a timezone member which seems not used now and its {{getObject}} returns Long(different with that in {{TimeStampXXVectors}} which returns {{LocalDateTime}}), should it return {{LocalDateTime}} with its timezone?
> Is it reasonable if we do as follows:
>  # replace Joda {{timezoneList}} with Java {{timezoneList}} in {{DateUtility}}
>  # add method like {{getLocalDateTimeFromEpochMilli(long epochMillis, String timezone)}} in DateUtility
>  # Not sure make {{TimeStampXXTZVectors}} return {{LocalDateTime}}?
> cc [~emkornfield@gmail.com]  [~bryanc]  [~siddteotia]



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)