You make a really good point on the potential for inconsistency between the
current version of the document and the version of the document that
contributed the rows in the stale view. I hadn’t been thinking about that when
I had made my earlier comment in this thread.
Adam
> On May 10, 2019,
Thanks everyone for the feedback. I've written up an RFC for this
https://github.com/apache/couchdb-documentation/pull/410
Hopefully, I've done a better job of explaining how the view signature will
be used. I've written up a section for when the document is emitted. I'm
having some doubts on
> On 15. Apr 2019, at 16:24, Garren Smith wrote:
>
> Hi Everyone,
>
> I want to start a discussion around creating map/reduce view indexes. One
> way to get views indexes to work with FoundationDB is to break up a view
> index into indexes for the map functions and indexes for the reduce
>
> On 15. Apr 2019, at 17:15, Will Holley wrote:
>
> Thanks Garren,
>
> As usual, a few questions :)
>
> 1. The data model suggests the idea of view groups gets carried over to
> fdb. Are there API / behaviour reasons to keep them? Would an index update
> transaction scope to a view group
On Tue, 16 Apr 2019, at 13:12, Garren Smith wrote:
> > 2. Regarding emitting doc as the value in a view function, this is so
> > common that I wonder if it's worth handling as a special case. It sounds
> > like there wouldn't be a solution for customers who use this technique to
> > ensure they
Hi Will,
Comments inline.
On Mon, Apr 15, 2019 at 5:24 PM Will Holley wrote:
> Thanks Garren,
>
> As usual, a few questions :)
>
> 1. The data model suggests the idea of view groups gets carried over to
> fdb. Are there API / behaviour reasons to keep them? Would an index update
> transaction
I could certainly see handling `emit(key, doc)` as a special case. I would feel
even better pursuing that special-case handling if we could characterize the
performance delta between a) executing the first range operation on the view
index + N additional range operations in paralle to retrieve
Thanks Garren,
As usual, a few questions :)
1. The data model suggests the idea of view groups gets carried over to
fdb. Are there API / behaviour reasons to keep them? Would an index update
transaction scope to a view group rather than a single view?
2. Regarding emitting doc as the value in a
Hi Everyone,
I want to start a discussion around creating map/reduce view indexes. One
way to get views indexes to work with FoundationDB is to break up a view
index into indexes for the map functions and indexes for the reduce
functions. Along those lines, I’m going to break the discussions into
