You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Pindikura Ravindra (JIRA)" <ji...@apache.org> on 2019/07/26 07:28:00 UTC
[jira] [Resolved] (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 ]
Pindikura Ravindra resolved ARROW-5967.
---------------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0
Issue resolved by pull request 4904
[https://github.com/apache/arrow/pull/4904]
> [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
> Labels: pull-request-available
> Fix For: 1.0.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> 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:
> # remove Joda {{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)