working on it *right now*.)
>>>
>>> ----- Original Message -
>>> From: "Eiri"
>>> To: dev@couchdb.apache.org
>>> Sent: Tuesday, April 3, 2018 8:15:21 AM
>>> Subject: Proposal: removing view changes code from mrview
>>>
the way, with my PMC hat on, you should unassign this issue
>> from yourself unless you're actively working on it *right now*.)
>>
>> - Original Message -
>> From: "Eiri"
>> To: dev@couchdb.apache.org
>> Sent: Tuesday, April 3, 2018 8:15:21 AM
uchdb.apache.org
> Sent: Tuesday, April 3, 2018 8:15:21 AM
> Subject: Proposal: removing view changes code from mrview
>
> Hi all,
>
> It is my understanding that a current implementation of view changes in
> mrview is conceptually broken. I heard from Robert Newson that
this issue from
yourself unless you're actively working on it *right now*.)
- Original Message -
From: "Eiri" <e...@eiri.ca>
To: dev@couchdb.apache.org
Sent: Tuesday, April 3, 2018 8:15:21 AM
Subject: Proposal: removing view changes code from mrview
Hi all,
It is
+1
Best Regards,
Peng Hui
From: Jan Lehnardt <j...@apache.org>
To: dev@couchdb.apache.org
Date: 03/04/2018 08:27 PM
Subject: Re: Proposal: removing view changes code from mrview
+1
> On 3. Apr 2018, at 14:15, Eiri <e...@eiri.ca> wrote:
>
> Hi all,
>
+1
> On 3. Apr 2018, at 14:15, Eiri wrote:
>
> Hi all,
>
> It is my understanding that a current implementation of view changes in
> mrview is conceptually broken. I heard from Robert Newson that he and
> Benjamin Bastian found that some time ago doing testing with deletion and
Hi all,
It is my understanding that a current implementation of view changes in mrview
is conceptually broken. I heard from Robert Newson that he and Benjamin Bastian
found that some time ago doing testing with deletion and recreation of docs
emitting same keys in the views.
I propose to