+1. Currently there is almost no way to write a moderately complex MR
job that doesn't spew deprecation warnings. It serves to endlessly
confuse newcomers to Hadoop.
On Wed, Apr 21, 2010 at 5:24 PM, Tom White t...@cloudera.com wrote:
The old MapReduce API in org.apache.hadoop.mapred was
Default output format for RandomTextWriter should be TextOutputFormat
-
Key: MAPREDUCE-1721
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1721
Project: Hadoop Map/Reduce
contrib/index - Upgrade to new Hadoop and Lucene API
Key: MAPREDUCE-1722
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1722
Project: Hadoop Map/Reduce
Issue Type: Improvement
Capacity Scheduler should allow configuration of Map Reduce task slots
independantly
---
Key: MAPREDUCE-1723
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1723
On the various pieces, I think:
0.20: -0 for removing the deprecation, +1 for improving the
deprecation message with links to the corresponding class.
0.21: new core api should be stable except for Job and Cluster
new library code should be evolving
-1 for removing the
+1
On Wed, Apr 21, 2010 at 2:24 PM, Tom White t...@cloudera.com wrote:
The old MapReduce API in org.apache.hadoop.mapred was deprecated in
the 0.20 release series when the new (Context Objects) MapReduce API
was added in org.apache.hadoop.mapreduce. Unfortunately, the new API
was not complete
Owen O'Malley wrote:
0.21: new core api should be stable except for Job and Cluster
new library code should be evolving
-1 for removing the deprecation, we need to
The Job API is central to the new API, no? Should we encourage
applications to move to the new API if it's not
+1 (mainly to avoid confusing new comers as Eric Sammer correctly
indicated).
On 4/22/2010 9:15 AM, Doug Cutting wrote:
Owen O'Malley wrote:
0.21: new core api should be stable except for Job and Cluster
new library code should be evolving
-1 for removing the deprecation, we
+1 for undeprecating. I think it's just being pragmatic.
Arun
On Apr 21, 2010, at 2:26 PM, Tom White t...@cloudera.com wrote:
The old MapReduce API in org.apache.hadoop.mapred was deprecated in
the 0.20 release series when the new (Context Objects) MapReduce API
was added in
Speaking for one power user (Pig) that did move to the new APIs,
moving that interface to evolving is a little unsettling. Is there a
feel for how much the new API is going to change?
Alan.
On Apr 21, 2010, at 2:24 PM, Tom White wrote:
The old MapReduce API in org.apache.hadoop.mapred
+1 for removing deprecation in 0.20.
+0 for removing deprecation in 0.21
Thanks
Amareshwari
On 4/22/10 7:25 PM, Owen O'Malley owen.omal...@gmail.com wrote:
On the various pieces, I think:
0.20: -0 for removing the deprecation, +1 for improving the
deprecation message with links to the
11 matches
Mail list logo