You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2017/04/28 09:58:04 UTC
[jira] [Resolved] (HADOOP-12837) FileStatus.getModificationTime
returns 0 for directories on S3n & S3a
[ https://issues.apache.org/jira/browse/HADOOP-12837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran resolved HADOOP-12837.
-------------------------------------
Resolution: Won't Fix
revisiting this. It's a wontfix I'm afraid. Sorry
> FileStatus.getModificationTime returns 0 for directories on S3n & S3a
> ---------------------------------------------------------------------
>
> Key: HADOOP-12837
> URL: https://issues.apache.org/jira/browse/HADOOP-12837
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/s3
> Reporter: Jagdish Kewat
> Priority: Minor
>
> Hi Team,
> We have observed an issue with the FileStatus.getModificationTime() API on S3 filesystem. The method always returns 0.
> I googled for this however couldn't find any solution as such which would fit in my scheme of things. S3FileStatus seems to be an option however I would be using this API on HDFS as well as S3 both so can't go for it.
> I tried to run the job on:
> * Release label:emr-4.2.0
> * Hadoop distribution:Amazon 2.6.0
> * Hadoop Common jar: hadoop-common-2.6.0.jar
> Please advise if any patch or fix available for this.
> Thanks,
> Jagdish
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org