[
https://issues.apache.org/jira/browse/HDFS-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013674#comment-13013674
]
Todd Lipcon commented on HDFS-1786:
-----------------------------------
Right now I cannot commit to 0.21 because the test is passing. If I add the
patch, the test starts to fail. Committing something that knowingly breaks
tests doesn't seem like the right move.
Looking at 0.21 more closely, it's not even properly set up to pull the
hadoop-common-0.21.1-SNAPSHOT from ivy - it's still building against an 0.21.0.
So, even though HADOOP-7174 was committed to common 0.21, it's not affecting
HDFS 0.21 yet. I flipped ivy/libraries.properties over to 0.21.1-SNAPSHOT and
now hdfs doesn't build at all - some issues related to Jasper that I can't
quite discern.
I will start a poll on the list to see if anyone would like to step up to
maintain the 0.21 branch. If no one does, we can vote to officially abandon it.
> Some cli test cases expect a "null" message
> -------------------------------------------
>
> Key: HDFS-1786
> URL: https://issues.apache.org/jira/browse/HDFS-1786
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: Uma Maheswara Rao G
> Priority: Minor
> Attachments: HDFS-1786.1.patch, HDFS-1786.patch, HDFS-1786_21.patch
>
>
> There are a few tests cases specified in {{TestHDFSCLI}} and {{TestDFSShell}}
> expecting "null" messages.
> e.g. in {{testHDFSConf.xml}},
> {code}
> <expected-output>get: null</expected-output>
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
