[
https://issues.apache.org/jira/browse/HDFS-11428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15887649#comment-15887649
]
Hadoop QA commented on HDFS-11428:
----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 9s{color}
| {color:red} HDFS-11428 does not apply to trunk. Rebase required? Wrong
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-11428 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12855002/HDFS-11428.004.patch |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/18466/console |
| Powered by | Apache Yetus 0.5.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> Change setErasureCodingPolicy to take a required string EC policy name
> ----------------------------------------------------------------------
>
> Key: HDFS-11428
> URL: https://issues.apache.org/jira/browse/HDFS-11428
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: erasure-coding
> Affects Versions: 3.0.0-alpha1
> Reporter: Andrew Wang
> Assignee: Andrew Wang
> Labels: hdfs-ec-3.0-must-do
> Attachments: HDFS-11428.001.patch, HDFS-11428.002.patch,
> HDFS-11428.003.patch, HDFS-11428.004.patch
>
>
> The current {{setErasureCodingPolicy}} API takes an optional {{ECPolicy}}.
> This makes calling the API harder for clients, since they need to turn a
> specified name into a policy, and the set of available EC policies is only
> available on the NN.
> You can see this awkwardness in the current EC cli set command: it first
> fetches the list of EC policies, looks for the one specified by the user,
> then calls set. This means we need to issue two RPCs for every set
> (inefficient), and we need to do validation on the NN side anyway (extraneous
> work).
> Since we're phasing out the system default EC policy, it also makes sense to
> make the policy a required parameter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
