hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bilahari T H (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-16479) ABFS FileStatus.getModificationTime returns localized time instead of UTC
Date Thu, 01 Aug 2019 12:18:00 GMT

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

Bilahari T H updated HADOOP-16479:
      Resolution: Fixed
    Release Note: 
private long parseLastModifiedTime(final String lastModifiedTime)

Timezone is part of lastModifiedTime String as it's last field. But when parsed it ignores
timezone field and assumes JVM timezone.
Fix: Made timezone field considered in lastModifiedTime when the same is parsed
          Status: Resolved  (was: Patch Available)

> ABFS FileStatus.getModificationTime returns localized time instead of UTC
> -------------------------------------------------------------------------
>                 Key: HADOOP-16479
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16479
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/azure
>    Affects Versions: 3.2.0
>            Reporter: Joan Sala Reixach
>            Assignee: Bilahari T H
>            Priority: Major
>         Attachments: HADOOP-16479-001.patch, image-2019-07-31-18-21-53-023.png, image-2019-07-31-18-23-37-349.png
> As per javadoc, the method FileStatus.getModificationTime() should return the time in
UTC, but it returns the time in the JVM timezone.
> The issue origins in AzureBlobFileSystemStore.getFileStatus() itself, sinceĀ  parseLastModifiedTime()
returns a wrong date. I have created a file in Azure Data Lake Gen2 and when I look atĀ  it
through the Azure Explorer it shows the correct modification time, but the method returns
-2 hours time (I am in CET = UTC+2).
> Azure Explorer last modified time:
> !image-2019-07-31-18-21-53-023.png|width=460,height=45!
> AbfsClient parseLastModifiedTime:
> !image-2019-07-31-18-23-37-349.png|width=459,height=284!
> It shows 15:21 CEST as utcDate, when it should be 15:21 UTC, which results in the 2 hour
> DateFormat.parse uses a localized calendar to parse dates which might be the source of
the issue.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message