It sounds like there's no strong objection to un-deprecating the old
API in 0.20 - I'll create a patch for this (see
https://issues.apache.org/jira/browse/MAPREDUCE-1734).
0.21 is less clear cut. However, if the new API were marked as
Evolving, then it's odd, to say the least, if the old API were
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
I don't have any issue with un-deprecating the old APIs. I agree if
changes are needed it's better to mark the new APIs to reflect it. I
just hope those changes can be kept as backward compatible as
possible. In particular with Job, Pig uses that in some of it's APIs
that it has
+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
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
