Here are the contents of part-0.deflate:
[r...@tyu-linux datajoin]# od output/part-0.deflate
000 116170 152163 032113 162064 002164 043222 047234 111040
020 010713 142115 022030 006142 030426 105406 015430 000561
040 021511 010444 130043 115010 32 167126 116422
056
Doe
Apologies if you received multiple copies of this message.
=
CALL FOR PAPERS
5th Workshop on
Virtualization in High-Performance Cloud Computing
VHPC'10
as part of Euro-Par 2010, Island of Ischia-Naples, Italy
==
[
https://issues.apache.org/jira/browse/HADOOP-6660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting resolved HADOOP-6660.
--
Resolution: Duplicate
Fix Version/s: (was: 0.22.0)
> add wrapper for Avro data
> --
DFSadmin commands setQuota and setSpaceQuota allowed when NameNode is in
safemode.
Key: HADOOP-6665
URL: https://issues.apache.org/jira/browse/HADOOP-6665
Project:
Tom White wrote:
I think the focus should be on getting an alpha release
out, so I suggest we create a new 0.21 branch from trunk
Another release we might consider is 1.0 based on 0.20. We'd then have
releases that correspond to what folks are actually using in production.
This would also r
> A 1.0 release based off 0.20 would give us a chance to state more precisely
> the 1.0 API that we intend to support long-term. For example, we might
> un-mark the old mapreduce APIs as deprecated in a 1.0 release, and mark the
> new mapreduce APIs as experimental and unstable there. Programs
On Mar 30, 2010, at 3:40 PM, Doug Cutting wrote:
Another release we might consider is 1.0 based on 0.20.
It is tempting and I think that 0.20 is *really* our 1.0, but I think
re-labeling a release a year after it came out would be confusing.
I think that we should change the rules so that
Introduce common logging mechanism to mark begin and end of test cases execution
Key: HADOOP-
URL: https://issues.apache.org/jira/browse/HADOOP-
Project: Hadoop C
[
https://issues.apache.org/jira/browse/HADOOP-6665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ravi Phulari resolved HADOOP-6665.
--
Resolution: Not A Problem
HDFS-185 fixed this issue.
> DFSadmin commands setQuota and setSpa