[ 
https://issues.apache.org/jira/browse/HADOOP-14430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024836#comment-16024836
 ] 

Hudson commented on HADOOP-14430:
---------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11782 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/11782/])
HADOOP-14430 the accessTime of FileStatus returned by SFTPFileSystem's (stevel: 
rev 8bf0e2d6b38a2cbd3c3d45557ede7575c1f18312)
* (edit) 
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/fs/sftp/TestSFTPFileSystem.java
* (edit) 
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/sftp/SFTPFileSystem.java


> the accessTime of FileStatus returned by SFTPFileSystem's getFileStatus 
> method is always 0
> ------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-14430
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14430
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 2.9.0, 3.0.0-alpha2
>            Reporter: Hongyuan Li
>            Assignee: Hongyuan Li
>            Priority: Trivial
>             Fix For: 2.9.0
>
>         Attachments: HADOOP-14430-001.patch, HADOOP-14430-002.patch
>
>
> the accessTime of FileStatus got by SFTPFileSystem's getFileStatus method is 
> always 0
> {{long accessTime = 0}} in code below; 
>   {code} private FileStatus getFileStatus(ChannelSftp channel, LsEntry 
> sftpFile,
>       Path parentPath) throws IOException {
>     SftpATTRS attr = sftpFile.getAttrs();
>    ……
>     long modTime = attr.getMTime() * 1000; // convert to milliseconds(This is 
> wrong too, according to HADOOP-14431
>     long accessTime = 0;
>   ……
>   }  {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to