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 deprecation
+1
On Wed, Apr 21, 2010 at 2:24 PM, Tom White 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 in 0.20 a
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 en
+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 ne
+1 for un-deprecating. I'm just being pragmatic.
Arun
On Apr 21, 2010, at 2:24 PM, Tom White 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. Unfortunate
+1 for undeprecating. I think it's just being pragmatic.
Arun
On Apr 21, 2010, at 2:26 PM, "Tom White" 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.
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 w
> * The next 0.20 release would have a non-deprecated old API.
+1
> * The forthcoming 0.21 release would have a "Stable" (non-deprecated)
> old API, and a "Evolving" new API.
+1
> * For some pre-1.0 release (perhaps 0.22), the old API could be
> deprecated again, and the new API marked as "Sta
+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" wrote:
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:
Alan,
On Apr 22, 2010, at 12:12 PM, Alan Gates wrote:
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?
The intent isn't to mark the 'new' apis as 'Evol
13 matches
Mail list logo
