On Apr 12, 2010, at 4:28 PM, Tom White wrote:
> On Mon, Apr 12, 2010 at 4:14 PM, Allen Wittenauer
> wrote:
>> So, does this mean that everything that has been committed for 0.22 is
>> actually going to be in 0.21? For example, symlinks were committed to trunk
>> for 0.22 according to JIRA.
>
On Mon, Apr 12, 2010 at 4:14 PM, Allen Wittenauer
wrote:
> So, does this mean that everything that has been committed for 0.22 is
> actually going to be in 0.21? For example, symlinks were committed to trunk
> for 0.22 according to JIRA.
Yes. Note that symlinks to date only work with the FileC
> So, does this mean that everything that has been committed for 0.22 is
> actually going to be in 0.21? For example, symlinks were committed >to trunk
> for 0.22 according to JIRA.
+1 for symlinks in next stable release and the associated refactoring of
isFile, isDirectory, etc.
___
So, does this mean that everything that has been committed for 0.22 is actually
going to be in 0.21? For example, symlinks were committed to trunk for 0.22
according to JIRA.
Hmm.. because of JIRA, would it be easier to actually call this release
0.22?
[
https://issues.apache.org/jira/browse/HADOOP-6507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-6507.
---
Hadoop Flags: [Reviewed]
Resolution: Fixed
I've just committed this. Thanks Corinne!
> Hadoop
Incorrect exit codes for "dfs -chown", "dfs -chgrp"
Key: HADOOP-6701
URL: https://issues.apache.org/jira/browse/HADOOP-6701
Project: Hadoop Common
Issue Type: Bug
Components: fs
