Hi there, I have a use case where I need to use a Chain Mapper and/or
Reducer. The problem is that
the AccumuloInputFormat extends hadoop.mapreduce.InputFormat rather than
implementing hadoop.mapred.InputFormat

Trying to make use of *org.apache.hadoop.mapred.lib.ChainMapper*
does not work because it requires the use of the mapred package. Is there a
version of the AccumuloInputFormat which uses
the hadoop.mapred package instead? Can InputFormatBase be rewritten with
the newer API?

Thanks!
Juan

Juan,
I believe the mapreduce API is the newer one.
Sent from my iPhone

On Jul 16, 2012, at 5:04 PM, Juan Moreno <[EMAIL PROTECTED]>
wrote:

Hi there, I have a use case where I need to use a Chain Mapper and/or
Reducer. The problem is that
the AccumuloInputFormat extends hadoop.mapreduce.InputFormat rather than
implementing hadoop.mapred.InputFormat

Trying to make use of *org.apache.hadoop.mapred.lib.ChainMapper*
does not work because it requires the use of the mapred package. Is there a
version of the AccumuloInputFormat which uses
the hadoop.mapred package instead? Can InputFormatBase be rewritten with
the newer API?

Thanks!
Juan

Jim is right.

Since the functions specified by ChainMapper are all done in the same
context, I htink you could write your Mapper and reducer to perform the
same functionality. Additionally, you could chain jobs, though that will
require a spill.

On Mon, Jul 16, 2012 at 5:05 PM, Jim Klucar <[EMAIL PROTECTED]> wrote:

> Juan,
> I believe the mapreduce API is the newer one.
>
>
> Sent from my iPhone
>
> On Jul 16, 2012, at 5:04 PM, Juan Moreno <[EMAIL PROTECTED]>
> wrote:
>
> Hi there, I have a use case where I need to use a Chain Mapper and/or
> Reducer. The problem is that
> the AccumuloInputFormat extends hadoop.mapreduce.InputFormat rather than
> implementing hadoop.mapred.InputFormat
>
> Trying to make use of *org.apache.hadoop.mapred.lib.ChainMapper*
> does not work because it requires the use of the mapred package. Is there
> a version of the AccumuloInputFormat which uses
> the hadoop.mapred package instead? Can InputFormatBase be rewritten with
> the newer API?
>
> Thanks!
> Juan
>
>

On Monday, July 16, 2012 5:02:52 PM, "Juan Moreno" <[EMAIL PROTECTED]> wrote:
> Hi there, I have a use case where I need to use a Chain Mapper and/or
> Reducer. The problem is that
> the AccumuloInputFormat extends hadoop.mapreduce.InputFormat rather
> than implementing hadoop.mapred.InputFormat
>
>
> Trying to make use of org.apache.hadoop.mapred.lib.ChainMapper
> does not work because it requires the use of the mapred package. Is
> there a version of the AccumuloInputFormat which uses
> the hadoop.mapred package instead? Can InputFormatBase be rewritten
> with the newer API?
>
>
> Thanks!
> Juan

I opened ACCUMULO-695 to add support for the old mapred API.

Billie

I would suggest spending the effort porting chainmapper to the new API
(mapreduce) since the old API will eventually be removed.

Sent from my smartphone. Please excuse any typos or shorthand.
On Jul 16, 2012 5:22 PM, "Billie J Rinaldi" <[EMAIL PROTECTED]>
wrote:

> On Monday, July 16, 2012 5:02:52 PM, "Juan Moreno" <
> [EMAIL PROTECTED]> wrote:
> > Hi there, I have a use case where I need to use a Chain Mapper and/or
> > Reducer. The problem is that
> > the AccumuloInputFormat extends hadoop.mapreduce.InputFormat rather
> > than implementing hadoop.mapred.InputFormat
> >
> >
> > Trying to make use of org.apache.hadoop.mapred.lib.ChainMapper
> > does not work because it requires the use of the mapred package. Is
> > there a version of the AccumuloInputFormat which uses
> > the hadoop.mapred package instead? Can InputFormatBase be rewritten
> > with the newer API?
> >
> >
> > Thanks!
> > Juan
>
> I opened ACCUMULO-695 to add support for the old mapred API.
>
> Billie
>

On Monday, July 16, 2012 5:27:09 PM, "Ed Kohlwey" <[EMAIL PROTECTED]> wrote:
> I would suggest spending the effort porting chainmapper to the new API
> (mapreduce) since the old API will eventually be removed.

I assumed that would be true since the old API was deprecated, and that is why we no longer support it.  However, the old API has been undeprecated since 0.20.205.0 and 1.0.0, which seems to indicate it's not going away.  Does anyone know what the plan for it is?

Billie
> Sent from my smartphone. Please excuse any typos or shorthand.
> On Jul 16, 2012 5:22 PM, "Billie J Rinaldi" <
> [EMAIL PROTECTED] > wrote:
>
>
> On Monday, July 16, 2012 5:02:52 PM, "Juan Moreno" <
> [EMAIL PROTECTED] > wrote:
> > Hi there, I have a use case where I need to use a Chain Mapper
> > and/or
> > Reducer. The problem is that
> > the AccumuloInputFormat extends hadoop.mapreduce.InputFormat rather
> > than implementing hadoop.mapred.InputFormat
> >
> >
> > Trying to make use of org.apache.hadoop.mapred.lib.ChainMapper
> > does not work because it requires the use of the mapred package. Is
> > there a version of the AccumuloInputFormat which uses
> > the hadoop.mapred package instead? Can InputFormatBase be rewritten
> > with the newer API?
> >
> >
> > Thanks!
> > Juan
>
> I opened ACCUMULO-695 to add support for the old mapred API.
>
> Billie

http://mail-archives.apache.org/mod_mbox/hadoop-common-user/201203.mbox/%3CCAOcnVr0osRAwytaU7LT+[EMAIL PROTECTED]%3E

It looks like the old API was given a second chance at life and is now
being billed as the "stable" API.

On Mon, Jul 16, 2012 at 2:39 PM, Billie J Rinaldi <[EMAIL PROTECTED]
> wrote:

> On Monday, July 16, 2012 5:27:09 PM, "Ed Kohlwey" <[EMAIL PROTECTED]>
> wrote:
> > I would suggest spending the effort porting chainmapper to the new API
> > (mapreduce) since the old API will eventually be removed.
>
> I assumed that would be true since the old API was deprecated, and that is
> why we no longer support it.  However, the old API has been undeprecated
> since 0.20.205.0 and 1.0.0, which seems to indicate it's not going away.
>  Does anyone know what the plan for it is?
>
> Billie
>
>
> > Sent from my smartphone. Please excuse any typos or shorthand.
> > On Jul 16, 2012 5:22 PM, "Billie J Rinaldi" <
> > [EMAIL PROTECTED] > wrote:
> >
> >
> > On Monday, July 16, 2012 5:02:52 PM, "Juan Moreno" <
> > [EMAIL PROTECTED] > wrote:
> > > Hi there, I have a use case where I need to use a Chain Mapper
> > > and/or
> > > Reducer. The problem is that
> > > the AccumuloInputFormat extends hadoop.mapreduce.InputFormat rather
> > > than implementing hadoop.mapred.InputFormat
> > >
> > >
> > > Trying to make use of org.apache.hadoop.mapred.lib.ChainMapper
> > > does not work because it requires the use of the mapred package. Is
> > > there a version of the AccumuloInputFormat which uses
> > > the hadoop.mapred package instead? Can InputFormatBase be rewritten
> > > with the newer API?
> > >
> > >
> > > Thanks!
> > > Juan
> >
> > I opened ACCUMULO-695 to add support for the old mapred API.
> >
> > Billie
>

The hadoop API is very confusing in that regard. Currently Accumulo runs
atop 0.20 and in that version , mapred is the new one and mapreduce is the
old one. InputFormat currently makes use of mapreduce.
On Jul 16, 2012 5:40 PM, "Billie J Rinaldi" <[EMAIL PROTECTED]>
wrote:

> On Monday, July 16, 2012 5:27:09 PM, "Ed Kohlwey" <[EMAIL PROTECTED]>
> wrote:
> > I would suggest spending the effort porting chainmapper to the new API
> > (mapreduce) since the old API will eventually be removed.
>
> I assumed that would be true since the old API was deprecated, and that is
> why we no longer support it.  However, the old API has been undeprecated
> since 0.20.205.0 and 1.0.0, which seems to indicate it's not going away.
>  Does anyone know what the plan for it is?
>
> Billie
>
>
> > Sent from my smartphone. Please excuse any typos or shorthand.
> > On Jul 16, 2012 5:22 PM, "Billie J Rinaldi" <
> > [EMAIL PROTECTED] > wrote:
> >
> >
> > On Monday, July 16, 2012 5:02:52 PM, "Juan Moreno" <
> > [EMAIL PROTECTED] > wrote:
> > > Hi there, I have a use case where I need to use a Chain Mapper
> > > and/or
> > > Reducer. The problem is that
> > > the AccumuloInputFormat extends hadoop.mapreduce.InputFormat rather
> > > than implementing hadoop.mapred.InputFormat
> > >
> > >
> > > Trying to make use of org.apache.hadoop.mapred.lib.ChainMapper
> > > does not work because it requires the use of the mapred package. Is
> > > there a version of the AccumuloInputFormat which uses
> > > the hadoop.mapred package instead? Can InputFormatBase be rewritten
> > > with the newer API?
> > >
> > >
> > > Thanks!
> > > Juan
> >
> > I opened ACCUMULO-695 to add support for the old mapred API.
> >
> > Billie
>

mapred was deprecated as of 0.20.0 (
http://hadoop.apache.org/common/docs/r0.20.0/api/org/apache/hadoop/mapred/InputFormat.html)
:)

On Mon, Jul 16, 2012 at 2:49 PM, Juan Moreno
<[EMAIL PROTECTED]>wrote:

> The hadoop API is very confusing in that regard. Currently Accumulo runs
> atop 0.20 and in that version , mapred is the new one and mapreduce is the
> old one. InputFormat currently makes use of mapreduce.
> On Jul 16, 2012 5:40 PM, "Billie J Rinaldi" <[EMAIL PROTECTED]>
> wrote:
>
>> On Monday, July 16, 2012 5:27:09 PM, "Ed Kohlwey" <[EMAIL PROTECTED]>
>> wrote:
>> > I would suggest spending the effort porting chainmapper to the new API
>> > (mapreduce) since the old API will eventually be removed.
>>
>> I assumed that would be true since the old API was deprecated, and that
>> is why we no longer support it.  However, the old API has been undeprecated
>> since 0.20.205.0 and 1.0.0, which seems to indicate it's not going away.
>>  Does anyone know what the plan for it is?
>>
>> Billie
>>
>>
>> > Sent from my smartphone. Please excuse any typos or shorthand.
>> > On Jul 16, 2012 5:22 PM, "Billie J Rinaldi" <
>> > [EMAIL PROTECTED] > wrote:
>> >
>> >
>> > On Monday, July 16, 2012 5:02:52 PM, "Juan Moreno" <
>> > [EMAIL PROTECTED] > wrote:
>> > > Hi there, I have a use case where I need to use a Chain Mapper
>> > > and/or
>> > > Reducer. The problem is that
>> > > the AccumuloInputFormat extends hadoop.mapreduce.InputFormat rather
>> > > than implementing hadoop.mapred.InputFormat
>> > >
>> > >
>> > > Trying to make use of org.apache.hadoop.mapred.lib.ChainMapper
>> > > does not work because it requires the use of the mapred package. Is
>> > > there a version of the AccumuloInputFormat which uses
>> > > the hadoop.mapred package instead? Can InputFormatBase be rewritten
>> > > with the newer API?
>> > >
>> > >
>> > > Thanks!
>> > > Juan
>> >
>> > I opened ACCUMULO-695 to add support for the old mapred API.
>> >
>> > Billie
>>
>

How hard would it be to implement own version using the mapred API ?

Would I have to do something as complex as InputFormatBase ? (It's a
mammoth class)
On Jul 16, 2012 5:53 PM, "William Slacum" <[EMAIL PROTECTED]>
wrote:

> mapred was deprecated as of 0.20.0 (
> http://hadoop.apache.org/common/docs/r0.20.0/api/org/apache/hadoop/mapred/InputFormat.html)
> :)
>
> On Mon, Jul 16, 2012 at 2:49 PM, Juan Moreno <[EMAIL PROTECTED]
> > wrote:
>
>> The hadoop API is very confusing in that regard. Currently Accumulo runs
>> atop 0.20 and in that version , mapred is the new one and mapreduce is the
>> old one. InputFormat currently makes use of mapreduce.
>>  On Jul 16, 2012 5:40 PM, "Billie J Rinaldi" <[EMAIL PROTECTED]>
>> wrote:
>>
>>> On Monday, July 16, 2012 5:27:09 PM, "Ed Kohlwey" <[EMAIL PROTECTED]>
>>> wrote:
>>> > I would suggest spending the effort porting chainmapper to the new API
>>> > (mapreduce) since the old API will eventually be removed.
>>>
>>> I assumed that would be true since the old API was deprecated, and that
>>> is why we no longer support it.  However, the old API has been undeprecated
>>> since 0.20.205.0 and 1.0.0, which seems to indicate it's not going away.
>>>  Does anyone know what the plan for it is?
>>>
>>> Billie
>>>
>>>
>>> > Sent from my smartphone. Please excuse any typos or shorthand.
>>> > On Jul 16, 2012 5:22 PM, "Billie J Rinaldi" <
>>> > [EMAIL PROTECTED] > wrote:
>>> >
>>> >
>>> > On Monday, July 16, 2012 5:02:52 PM, "Juan Moreno" <
>>> > [EMAIL PROTECTED] > wrote:
>>> > > Hi there, I have a use case where I need to use a Chain Mapper
>>> > > and/or
>>> > > Reducer. The problem is that
>>> > > the AccumuloInputFormat extends hadoop.mapreduce.InputFormat rather
>>> > > than implementing hadoop.mapred.InputFormat
>>> > >
>>> > >
>>> > > Trying to make use of org.apache.hadoop.mapred.lib.ChainMapper
>>> > > does not work because it requires the use of the mapred package. Is
>>> > > there a version of the AccumuloInputFormat which uses
>>> > > the hadoop.mapred package instead? Can InputFormatBase be rewritten
>>> > > with the newer API?
>>> > >
>>> > >
>>> > > Thanks!
>>> > > Juan
>>> >
>>> > I opened ACCUMULO-695 to add support for the old mapred API.
>>> >
>>> > Billie
>>>
>>
>

You'd basically be doing a copy of the getInputSplits and getRecordReader
methods, except they'd be returning the mapred version of those classes.

On Mon, Jul 16, 2012 at 3:13 PM, Juan Moreno
<[EMAIL PROTECTED]>wrote:

> How hard would it be to implement own version using the mapred API ?
>
> Would I have to do something as complex as InputFormatBase ? (It's a
> mammoth class)
> On Jul 16, 2012 5:53 PM, "William Slacum" <[EMAIL PROTECTED]>
> wrote:
>
>> mapred was deprecated as of 0.20.0 (
>> http://hadoop.apache.org/common/docs/r0.20.0/api/org/apache/hadoop/mapred/InputFormat.html)
>> :)
>>
>> On Mon, Jul 16, 2012 at 2:49 PM, Juan Moreno <
>> [EMAIL PROTECTED]> wrote:
>>
>>> The hadoop API is very confusing in that regard. Currently Accumulo runs
>>> atop 0.20 and in that version , mapred is the new one and mapreduce is the
>>> old one. InputFormat currently makes use of mapreduce.
>>>  On Jul 16, 2012 5:40 PM, "Billie J Rinaldi" <[EMAIL PROTECTED]>
>>> wrote:
>>>
>>>> On Monday, July 16, 2012 5:27:09 PM, "Ed Kohlwey" <[EMAIL PROTECTED]>
>>>> wrote:
>>>> > I would suggest spending the effort porting chainmapper to the new API
>>>> > (mapreduce) since the old API will eventually be removed.
>>>>
>>>> I assumed that would be true since the old API was deprecated, and that
>>>> is why we no longer support it.  However, the old API has been undeprecated
>>>> since 0.20.205.0 and 1.0.0, which seems to indicate it's not going away.
>>>>  Does anyone know what the plan for it is?
>>>>
>>>> Billie
>>>>
>>>>
>>>> > Sent from my smartphone. Please excuse any typos or shorthand.
>>>> > On Jul 16, 2012 5:22 PM, "Billie J Rinaldi" <
>>>> > [EMAIL PROTECTED] > wrote:
>>>> >
>>>> >
>>>> > On Monday, July 16, 2012 5:02:52 PM, "Juan Moreno" <
>>>> > [EMAIL PROTECTED] > wrote:
>>>> > > Hi there, I have a use case where I need to use a Chain Mapper
>>>> > > and/or
>>>> > > Reducer. The problem is that
>>>> > > the AccumuloInputFormat extends hadoop.mapreduce.InputFormat rather
>>>> > > than implementing hadoop.mapred.InputFormat
>>>> > >
>>>> > >
>>>> > > Trying to make use of org.apache.hadoop.mapred.lib.ChainMapper
>>>> > > does not work because it requires the use of the mapred package. Is
>>>> > > there a version of the AccumuloInputFormat which uses
>>>> > > the hadoop.mapred package instead? Can InputFormatBase be rewritten
>>>> > > with the newer API?
>>>> > >
>>>> > >
>>>> > > Thanks!
>>>> > > Juan
>>>> >
>>>> > I opened ACCUMULO-695 to add support for the old mapred API.
>>>> >
>>>> > Billie
>>>>
>>>
>>

Perhaps it would be easier to keep those methods intact and have a
translation method?

Sent from my phone, so pardon the typos and brevity.
On Jul 16, 2012 6:21 PM, "William Slacum" <[EMAIL PROTECTED]>
wrote:

> You'd basically be doing a copy of the getInputSplits and getRecordReader
> methods, except they'd be returning the mapred version of those classes.
>
> On Mon, Jul 16, 2012 at 3:13 PM, Juan Moreno <[EMAIL PROTECTED]
> > wrote:
>
>> How hard would it be to implement own version using the mapred API ?
>>
>> Would I have to do something as complex as InputFormatBase ? (It's a
>> mammoth class)
>> On Jul 16, 2012 5:53 PM, "William Slacum" <[EMAIL PROTECTED]>
>> wrote:
>>
>>> mapred was deprecated as of 0.20.0 (
>>> http://hadoop.apache.org/common/docs/r0.20.0/api/org/apache/hadoop/mapred/InputFormat.html)
>>> :)
>>>
>>> On Mon, Jul 16, 2012 at 2:49 PM, Juan Moreno <
>>> [EMAIL PROTECTED]> wrote:
>>>
>>>> The hadoop API is very confusing in that regard. Currently Accumulo
>>>> runs atop 0.20 and in that version , mapred is the new one and mapreduce is
>>>> the old one. InputFormat currently makes use of mapreduce.
>>>>  On Jul 16, 2012 5:40 PM, "Billie J Rinaldi" <[EMAIL PROTECTED]>
>>>> wrote:
>>>>
>>>>> On Monday, July 16, 2012 5:27:09 PM, "Ed Kohlwey" <[EMAIL PROTECTED]>
>>>>> wrote:
>>>>> > I would suggest spending the effort porting chainmapper to the new
>>>>> API
>>>>> > (mapreduce) since the old API will eventually be removed.
>>>>>
>>>>> I assumed that would be true since the old API was deprecated, and
>>>>> that is why we no longer support it.  However, the old API has been
>>>>> undeprecated since 0.20.205.0 and 1.0.0, which seems to indicate it's not
>>>>> going away.  Does anyone know what the plan for it is?
>>>>>
>>>>> Billie
>>>>>
>>>>>
>>>>> > Sent from my smartphone. Please excuse any typos or shorthand.
>>>>> > On Jul 16, 2012 5:22 PM, "Billie J Rinaldi" <
>>>>> > [EMAIL PROTECTED] > wrote:
>>>>> >
>>>>> >
>>>>> > On Monday, July 16, 2012 5:02:52 PM, "Juan Moreno" <
>>>>> > [EMAIL PROTECTED] > wrote:
>>>>> > > Hi there, I have a use case where I need to use a Chain Mapper
>>>>> > > and/or
>>>>> > > Reducer. The problem is that
>>>>> > > the AccumuloInputFormat extends hadoop.mapreduce.InputFormat rather
>>>>> > > than implementing hadoop.mapred.InputFormat
>>>>> > >
>>>>> > >
>>>>> > > Trying to make use of org.apache.hadoop.mapred.lib.ChainMapper
>>>>> > > does not work because it requires the use of the mapred package. Is
>>>>> > > there a version of the AccumuloInputFormat which uses
>>>>> > > the hadoop.mapred package instead? Can InputFormatBase be rewritten
>>>>> > > with the newer API?
>>>>> > >
>>>>> > >
>>>>> > > Thanks!
>>>>> > > Juan
>>>>> >
>>>>> > I opened ACCUMULO-695 to add support for the old mapred API.
>>>>> >
>>>>> > Billie
>>>>>
>>>>
>>>
>

I think I remember the deprecation markings reappearing in 2.0 alpha. I'm
not at a computer right now to confirm though.

Sent from my smartphone. Please excuse any typos or shorthand.
On Jul 16, 2012 6:37 PM, "John Vines" <[EMAIL PROTECTED]> wrote:

> Perhaps it would be easier to keep those methods intact and have a
> translation method?
>
> Sent from my phone, so pardon the typos and brevity.
> On Jul 16, 2012 6:21 PM, "William Slacum" <[EMAIL PROTECTED]>
> wrote:
>
>> You'd basically be doing a copy of the getInputSplits and getRecordReader
>> methods, except they'd be returning the mapred version of those classes.
>>
>> On Mon, Jul 16, 2012 at 3:13 PM, Juan Moreno <
>> [EMAIL PROTECTED]> wrote:
>>
>>> How hard would it be to implement own version using the mapred API ?
>>>
>>> Would I have to do something as complex as InputFormatBase ? (It's a
>>> mammoth class)
>>> On Jul 16, 2012 5:53 PM, "William Slacum" <
>>> [EMAIL PROTECTED]> wrote:
>>>
>>>> mapred was deprecated as of 0.20.0 (
>>>> http://hadoop.apache.org/common/docs/r0.20.0/api/org/apache/hadoop/mapred/InputFormat.html)
>>>> :)
>>>>
>>>> On Mon, Jul 16, 2012 at 2:49 PM, Juan Moreno <
>>>> [EMAIL PROTECTED]> wrote:
>>>>
>>>>> The hadoop API is very confusing in that regard. Currently Accumulo
>>>>> runs atop 0.20 and in that version , mapred is the new one and mapreduce is
>>>>> the old one. InputFormat currently makes use of mapreduce.
>>>>>  On Jul 16, 2012 5:40 PM, "Billie J Rinaldi" <
>>>>> [EMAIL PROTECTED]> wrote:
>>>>>
>>>>>> On Monday, July 16, 2012 5:27:09 PM, "Ed Kohlwey" <[EMAIL PROTECTED]>
>>>>>> wrote:
>>>>>> > I would suggest spending the effort porting chainmapper to the new
>>>>>> API
>>>>>> > (mapreduce) since the old API will eventually be removed.
>>>>>>
>>>>>> I assumed that would be true since the old API was deprecated, and
>>>>>> that is why we no longer support it.  However, the old API has been
>>>>>> undeprecated since 0.20.205.0 and 1.0.0, which seems to indicate it's not
>>>>>> going away.  Does anyone know what the plan for it is?
>>>>>>
>>>>>> Billie
>>>>>>
>>>>>>
>>>>>> > Sent from my smartphone. Please excuse any typos or shorthand.
>>>>>> > On Jul 16, 2012 5:22 PM, "Billie J Rinaldi" <
>>>>>> > [EMAIL PROTECTED] > wrote:
>>>>>> >
>>>>>> >
>>>>>> > On Monday, July 16, 2012 5:02:52 PM, "Juan Moreno" <
>>>>>> > [EMAIL PROTECTED] > wrote:
>>>>>> > > Hi there, I have a use case where I need to use a Chain Mapper
>>>>>> > > and/or
>>>>>> > > Reducer. The problem is that
>>>>>> > > the AccumuloInputFormat extends hadoop.mapreduce.InputFormat
>>>>>> rather
>>>>>> > > than implementing hadoop.mapred.InputFormat
>>>>>> > >
>>>>>> > >
>>>>>> > > Trying to make use of org.apache.hadoop.mapred.lib.ChainMapper
>>>>>> > > does not work because it requires the use of the mapred package.
>>>>>> Is
>>>>>> > > there a version of the AccumuloInputFormat which uses
>>>>>> > > the hadoop.mapred package instead? Can InputFormatBase be
>>>>>> rewritten
>>>>>> > > with the newer API?
>>>>>> > >
>>>>>> > >
>>>>>> > > Thanks!
>>>>>> > > Juan
>>>>>> >
>>>>>> > I opened ACCUMULO-695 to add support for the old mapred API.
>>>>>> >
>>>>>> > Billie
>>>>>>
>>>>>
>>>>
>>

On 07/16/2012 07:20 PM, Ed Kohlwey wrote:
> I think I remember the deprecation markings reappearing in 2.0 alpha.
> I'm not at a computer right now to confirm though.

The official word whenever this question comes up on the Hadoop mailing
lists is that mapred has been undeprecated and there is no particular
plan to officially implement ChainMapper/ChainReducer or any of the
dozen other Nice Things that mapred has in the mapreduce context.

Thanks for the heads up; that really bites.

In that case, it seems I'll just try to create a custom Input and Output
Format using the mapred api.

I will submit a patch to ACCUMULO-695 if I make something interesting.
Thanks!
On Jul 17, 2012 11:46 AM, "John Armstrong" <[EMAIL PROTECTED]> wrote:

> On 07/16/2012 07:20 PM, Ed Kohlwey wrote:
>
>> I think I remember the deprecation markings reappearing in 2.0 alpha.
>> I'm not at a computer right now to confirm though.
>>
>
> The official word whenever this question comes up on the Hadoop mailing
> lists is that mapred has been undeprecated and there is no particular plan
> to officially implement ChainMapper/ChainReducer or any of the dozen other
> Nice Things that mapred has in the mapreduce context.
>