You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Ying Bian <yb...@me.com> on 2016/02/27 14:36:31 UTC
Is mango a full replacement of the original map/reduce API?
Hi All,
I know we introduced mango in couchdb 2.0. While having not tried that out, I want to ask this simple question:
Is mango a full replacement of the the original map/reduce API? i.e: Can it do everything that the old map/reduce
API does? If not, in which cases that I still need to use map/reduce?
-Ying
Re: Is mango a full replacement of the original map/reduce API?
Posted by Ying Bian <yb...@me.com>.
Got it. Thanks for your quick response.
-Ying
> 在 2016年2月27日，21:40，Alexander Shorin <kx...@gmail.com> 写道：
>
> Hi,
>
> Mango is not a replacement of M/R, but a DSL that works on top of M/R
> hiding the implementation details from you. Due to a limited nature,
> it cannot be a complete replacement of JS and else M/R function, only
> for a subset of simple and trivial ones.
> --
> ,,,^..^,,,
>
>
> On Sat, Feb 27, 2016 at 4:36 PM, Ying Bian <yb...@me.com> wrote:
>> Hi All,
>>
>> I know we introduced mango in couchdb 2.0. While having not tried that out, I want to ask this simple question:
>> Is mango a full replacement of the the original map/reduce API? i.e: Can it do everything that the old map/reduce
>> API does? If not, in which cases that I still need to use map/reduce?
>>
>> -Ying
Re: Is mango a full replacement of the original map/reduce API?
Posted by Alexander Shorin <kx...@gmail.com>.
Hi,
Mango is not a replacement of M/R, but a DSL that works on top of M/R
hiding the implementation details from you. Due to a limited nature,
it cannot be a complete replacement of JS and else M/R function, only
for a subset of simple and trivial ones.
--
,,,^..^,,,
On Sat, Feb 27, 2016 at 4:36 PM, Ying Bian <yb...@me.com> wrote:
> Hi All,
>
> I know we introduced mango in couchdb 2.0. While having not tried that out, I want to ask this simple question:
> Is mango a full replacement of the the original map/reduce API? i.e: Can it do everything that the old map/reduce
> API does? If not, in which cases that I still need to use map/reduce?
>
> -Ying