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

Lei (Eddy) Xu updated HADOOP-14398:
-----------------------------------
    Attachment: HADOOP-14398.02.patch

Thanks for the reviews, [~andrew.wang]

bq. be invoked . 
bq. there's a typo in the builder doc: "recurisve"
bq. Would be better to use an fake "FooFileSystem"

Fixed. 

bq. a behavior change compared to the current create APIs,
bq. Should we also call out the change in default behavior compared to the 
existing create call?

{{overwrite}} is the same as {{FS#create}}. while {{recursive()}} is changed. 
Modified in the doc. I think they are the only changes. 

bq. Are there provisions for probing FS capabilities without must 

It does not have this capability now. We can discuss it in follow on JIRAs.

bq. move the HDFS-specific builder parameters to an HDFS-specific page

Nice suggestions. There are a few places in {{ilesystem.md}} mentioned HDFS 
special cases, and I did not find a good and existing place to put this into 
HDFS section in the doc.  Besides, it offers the single place for user to look 
up what the Builder is capable of. Shall we put it here?

Thanks!



> Modify documents for the FileSystem Builder API
> -----------------------------------------------
>
>                 Key: HADOOP-14398
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14398
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs
>    Affects Versions: 3.0.0-alpha3
>            Reporter: Lei (Eddy) Xu
>            Assignee: Lei (Eddy) Xu
>              Labels: docuentation
>         Attachments: HADOOP-14398.00.patch, HADOOP-14398.01.patch, 
> HADOOP-14398.02.patch
>
>
> After finishes the API, we should update the document to describe the 
> interface, capability and contract which the APIs hold. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to