+1
On Tue, Apr 3, 2018 at 9:23 AM, Joan Touzet wrote:
> +1.
>
> 1. No one has worked on a fix since its contribution prior to 2.0.
> 2. The code will always be in git in an older revision if someone is
> looking for it.
> 3. We have #592 which describes the fundamental
+1.
1. No one has worked on a fix since its contribution prior to 2.0.
2. The code will always be in git in an older revision if someone is looking
for it.
3. We have #592 which describes the fundamental problem that needs to be
resolved. (By the way, with my PMC hat on, you should unassign
+1
Best Regards,
Peng Hui
From: Jan Lehnardt
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 wrote:
>
> Hi all,
>
> It is my understanding
+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