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

SammiChen commented on HDFS-10996:
----------------------------------

Hi Andrew, thanks for reviewing the patch!  Yes. it seems the new create API 
has a lot of parameters.  A builder-based API will be helpful to user.  I will 
create a separate JIRA for it later. 
Talking about refactor, I have several questions. I would like to consult you. 
1. The refactor is about create API. There are create APIs in both 
{{FileSystem}} abstract class and {{ClientProtocol}} interface. I think its 
create API in {{FileSystem}} need to be refactored. end user is not supposed to 
call functions of {{ClientProtocol}} directory. 
2. To keep backward compatibility, we should add new builder based create APIs, 
and not change current create APIs. And the scope of these new builder based 
create APIs, put them only in {{DistributedFileSystme}} class or in 
{{FileSystem}} class.
Tell me if you have different opinions. 

> Ability to specify per-file EC policy at create time
> ----------------------------------------------------
>
>                 Key: HDFS-10996
>                 URL: https://issues.apache.org/jira/browse/HDFS-10996
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: erasure-coding
>    Affects Versions: 3.0.0-alpha1
>            Reporter: Andrew Wang
>            Assignee: SammiChen
>         Attachments: HDFS-10996-v1.patch, HDFS-10996-v2.patch, 
> HDFS-10996-v3.patch
>
>
> Based on discussion in HDFS-10971, it would be useful to specify the EC 
> policy when the file is created. This is useful for situations where app 
> requirements do not map nicely to the current directory-level policies.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to