Thanks for the quick reply,
I was hoping to use something similar to the one used on the couchbase manager:
I noticed that you are using the docs endpoint with the startkey and endkey, and that’s what I need, but it is not referenced in your REST API documentation.
Other databases based on the work of CouchDB have this capability and it seems a good way to avoid creating views.
I don’t understand why we need aggregation to lookup for keys since we already have the primary index constructed. (the idea is to avoid the construction of another index).
Can you explain in more detail what would be the overhead in this approach and if is there any way to use the same feature you are using in your maintenance application.