[
https://issues.apache.org/jira/browse/HADOOP-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Kimball updated HADOOP-5901:
----------------------------------
Attachment: HADOOP-5901.4.patch
Here's another take at this with IllegalArgumentException behavior restored.
MapReduce compilation is ok with this since it does not change the
statically-typed API. (If this is committed, MAPREDUCE-1297 should be resolved
as Invalid.)
I've posted a patch at HDFS-835 to handle the HDFS test failure that occurred
the first time this was committed. If this patch is committed, HDFS-835 should
be committed as well.
> FileSystem.fixName() has unexpected behaviour
> ---------------------------------------------
>
> Key: HADOOP-5901
> URL: https://issues.apache.org/jira/browse/HADOOP-5901
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 0.21.0
> Reporter: Steve Loughran
> Assignee: Aaron Kimball
> Priority: Minor
> Fix For: 0.22.0
>
> Attachments: HADOOP-5901.2.patch, HADOOP-5901.3.patch,
> HADOOP-5901.4.patch, HADOOP-5901.patch
>
>
> {{FileSystem.fixName()}} tries to patch up fs.default.name values, but I'm
> not sure it helps that well.
> Has it been warning about deprecated values for long enough for it to be
> turned off?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
