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?
Hi Owen,
Thanks for your offer to review the work I've been doing on
compatibility. If pushing back the freeze date will help us stabilize
the public API, then I'm OK moving it to 30 April.
On the serialization changes, I'm +1 to backing out the changes since
0.20 rather than trying to get new ch
On Fri, Apr 9, 2010 at 5:16 PM, Doug Cutting wrote:
> Is this just HADOOP-6685? Or does it also include MAPREDUCE-1183?
>
I just meant h-6685.
My instinct would rather be to revert the serialization API changes made
> since 0.20 (mostly HADOOP-6165) if that's not an API we intend to support,
>
Owen O'Malley wrote:
and hopefully to get the new generic serialization api in before the
branch.
Is this just HADOOP-6685? Or does it also include MAPREDUCE-1183?
My instinct would rather be to revert the serialization API changes made
since 0.20 (mostly HADOOP-6165) if that's not an API we
On Apr 9, 2010, at 11:10 AM, Tom White wrote:
Next Friday (16 April) is the feature freeze date for the new 0.21
branch.
I've been buried by security work and would really love to have some
more time to review API annotations, look at the jdiffs for the apis,
and hopefully to get the new
I wanted to send an update on my plans for doing a 0.21 Hadoop Release.
Next Friday (16 April) is the feature freeze date for the new 0.21
branch. On that date I will create new 0.21 branches for Common, HDFS,
and MapReduce (I will rename the old branches so history is not lost),
and update the CH
