[
https://issues.apache.org/jira/browse/HADOOP-16479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16903205#comment-16903205
]
Hudson commented on HADOOP-16479:
---------------------------------
FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #17065 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/17065/])
HADOOP-16479. ABFS FileStatus.getModificationTime returns localized time
(stevel: rev 5840df86d7a9e79007745688313f1d799d89189b)
* (edit)
hadoop-tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azurebfs/AzureBlobFileSystemStore.java
* (edit)
hadoop-tools/hadoop-azure/src/test/java/org/apache/hadoop/fs/azurebfs/ITestAzureBlobFileSystemFileStatus.java
> 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
> Fix For: 3.3.0
>
> Attachments: HADOOP-16479-001.patch, HADOOP-16479-002.patch,
> HADOOP-16479-003.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 loss.
> DateFormat.parse uses a localized calendar to parse dates which might be the
> source of the issue.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
