[
https://issues.apache.org/jira/browse/HDFS-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039741#comment-13039741
]
Harsh J Chouraria commented on HDFS-1636:
-----------------------------------------
Failing system test framework compile appears to be cause of missing
DFSConfigKeys. I'm positive I haven't touched that one here.
{code}
[exec] -compile-fault-inject:
[exec] [echo] Start weaving aspects in place
[exec] [iajc]
/grid/0/hudson/hudson-slave/workspace/PreCommit-HDFS-Build/trunk/src/test/system/java/org/apache/hadoop/hdfs/test/system/HDFSDaemonClient.java:38
[error] DFSConfigKeys cannot be resolved
[exec] [iajc] DFSConfigKeys.DFS_DATANODE_DATA_DIR_KEY);
[exec] [iajc] ^^^^
[exec] [iajc]
/grid/0/hudson/hudson-slave/workspace/PreCommit-HDFS-Build/trunk/src/test/system/java/org/apache/hadoop/hdfs/test/system/HDFSDaemonClient.java:43
[error] DFSConfigKeys cannot be resolved
[exec] [iajc] DFSConfigKeys.DFS_NAMENODE_NAME_DIR_KEY)[0];
[exec] [iajc] ^^^^
[exec] [iajc]
[exec] [iajc] 2 errors
{code}
> If dfs.name.dir points to an empty dir, namenode format shouldn't require
> confirmation
> --------------------------------------------------------------------------------------
>
> Key: HDFS-1636
> URL: https://issues.apache.org/jira/browse/HDFS-1636
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Harsh J Chouraria
> Priority: Minor
> Fix For: 0.23.0
>
> Attachments: HDFS-1636.r1.diff, HDFS-1636.r2.diff, HDFS-1636.r3.diff
>
>
> Right now, running namenode -format when dfs.name.dir is configured to a dir
> which exists but is empty still asks for confirmation. This is unnecessary
> since it isn't blowing away any real data.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
