[
https://issues.apache.org/jira/browse/HDFS-9005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213269#comment-15213269
]
Allen Wittenauer commented on HDFS-9005:
----------------------------------------
It's concerning that:
a) anyone would even suggest that it is ok to add a file that fails the ASF
license check
b) no one bothered to see how the *other* JSON files are handled in the source
tree
c) there are a ton of watchers (including PMC) and not a single one of you said
anything
To save you folks some time: no, it's not OK to just let a license violation
hang out in the source tree. Never ever ever. That's an instant "do not
commit." No, you don't need to generate it dynamically. Just add the file to
the RAT exclusions list in the pom file and all will be well.
Next up, is there a reason why the fix version is set to both 2.8.0 and 3.0.0?
> Provide support for upgrade domain script
> -----------------------------------------
>
> Key: HDFS-9005
> URL: https://issues.apache.org/jira/browse/HDFS-9005
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Ming Ma
> Assignee: Ming Ma
> Fix For: 3.0.0, 2.8.0
>
> Attachments: HDFS-9005-2.patch, HDFS-9005-3.patch, HDFS-9005-4.patch,
> HDFS-9005.patch
>
>
> As part of the upgrade domain feature, we need to provide a mechanism to
> specify upgrade domain for each datanode. One way to accomplish that is to
> allow admins specify an upgrade domain script that takes DN ip or hostname as
> input and return the upgrade domain. Then namenode will use it at run time to
> set {{DatanodeInfo}}'s upgrade domain string. The configuration can be
> something like:
> {noformat}
> <property>
> <name>dfs.namenode.upgrade.domain.script.file.name</name>
> <value>/etc/hadoop/conf/upgrade-domain.sh</value>
> </property>
> {noformat}
> just like topology script,
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
