On 19 Nov 2009, at 02:16, Li Zhengji wrote:
Hi,
On Thu, Nov 19, 2009 at 12:46 AM, Adam Kocoloski kocol...@apache.org wrote:
Hi,
We already do this -- if two views in a design document have byte-identical
map functions, the map is only run once, the index is only saved once, and
the
Hi Jan,
On Thu, Nov 19, 2009 at 9:50 PM, Jan Lehnardt j...@apache.org wrote:
Why is the current implementation not a good idea? It works well :)
Cheers
Jan
--
Because it's not a good idea to implement the same thing several
times. Bulbs work well, but compact fluorescent lamps are better,
On Thu, Nov 19, 2009 at 7:06 PM, Li Zhengji zhengji...@gmail.com wrote:
Hi Jan,
On Thu, Nov 19, 2009 at 9:50 PM, Jan Lehnardt j...@apache.org wrote:
Why is the current implementation not a good idea? It works well :)
Cheers
Jan
--
Because it's not a good idea to implement the same thing
Hi all,
I am planning to use CouchDB now, and coming into some thoughts today,
which may be silly.
1. One map, multiple reduces.
There are possibilities that multiple views share the same map
function. Then, I think these views could be combined, sharing the
same map function. The outcome is
Hi,
On Nov 18, 2009, at 4:17 AM, Li Zhengji wrote:
Hi all,
I am planning to use CouchDB now, and coming into some thoughts today,
which may be silly.
1. One map, multiple reduces.
There are possibilities that multiple views share the same map
function. Then, I think these views could
Hi,
On Thu, Nov 19, 2009 at 12:46 AM, Adam Kocoloski kocol...@apache.org wrote:
Hi,
We already do this -- if two views in a design document have byte-identical
map functions, the map is only run once, the index is only saved once, and
the different reduce functions share that index.
I
