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

Mingliang Liu updated HADOOP-13946:
-----------------------------------
    Attachment: Screen Shot 2017-03-07 at 3.44.43 PM.png

Chris' comment makes sense to me. I slightly changed the v4 patch and uploaded 
the v5 one for addressing that. Specially, the "*but" was changed to "but" 
removing the "*". I think we can live without that. For wasb:// linking problem 
I used ` to wrap it as code as `wasb://`. Also fixed typo "artificially".

Preview from my screenshot [#Screen Shot 2017-03-07 at 3.44.43 PM.png].

I'm assuming the v5 patch inherits all the +1s on v4 patch; will commit in 3 
days if no objections.

> Document how HDFS updates timestamps in the FS spec; compare with object 
> stores
> -------------------------------------------------------------------------------
>
>                 Key: HADOOP-13946
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13946
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: documentation, fs
>    Affects Versions: 2.7.3
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Minor
>         Attachments: HADOOP-13946-001.patch, HADOOP-13946-002.patch, 
> HADOOP-13946-003.patch, HADOOP-13946-004.patch, HADOOP-13946-005.patch, 
> Screen Shot 2017-03-07 at 3.44.43 PM.png
>
>
> SPARK-17159 shows that the behavior of when HDFS updates timestamps isn't 
> well documented. Document these in the FS spec.
> I'm not going to add tests for this, as it is so very dependent on FS 
> implementations, as in "POSIX filesystems may behave differently from HDFS". 
> If someone knows what happens there, their contribution is welcome.



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

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

Reply via email to