Re: [DISCUSS] Implementing Mango Indexes for FoundationDB

Hi Will, great comments, I have replies to a couple of them. > On Apr 1, 2019, at 5:21 AM, Will Holley wrote: > > 2. Does the ICU sort key have a bounded length? Mostly I'm wondering > whether we can guarantee that the generated keys will fit within the > maximum FDB key length or if there

Re: [DISCUSS] Implementing Mango Indexes for FoundationDB

> On Apr 1, 2019, at 2:21 AM, Will Holley wrote: > > 5. I have a few concerns about the performance given we'll no longer be > able to push down filtering to the data storage tier. It sounds [1] like a > key thing will be the extent to which we can concurrently fetch/filter > non-overlapping

Re: [DISCUSS] : things we need to solve/decide : storing JSON documents

I went and collected this discussion into an RFC proposing the “exploded KV” approach: https://github.com/apache/couchdb-documentation/pull/403 Cheers, Adam > On Feb 20, 2019, at 10:47 AM, Paul Davis wrote: > > Strongly agree that

[DISCUSS] Session token invalidation

Hello all, my name is Tabeth and this is my first post. Please let me know if I'm not following any conventions surrounding the usage of this mailing list. Without further ado: I believe it would be prudent for CouchDB to add the ability to invalidate specific sessions. There was some

Re: [DISCUSS] Implementing Mango Indexes for FoundationDB

Thanks for kicking this off Garren! I have a few questions / thoughts: 1. Will these indexes continue to have associated design documents? I assume this aspect wouldn't change, but it would be good to be explicit. Aside from being required for replication, it's useful to be able to query the