Skip to content

Conversation

@processnull
Copy link

avoid conflicts when run couchDB with flags --admin=user:pass because this flag adds credentials at the end of the file in domains of [dreyfus] not [admins]

avoid conflicts when run couchDB with flags --admin=user:pass because this flag adds credentials at the end of the file in domains of [dreyfus] not [admins]
@nickva nickva closed this in cba29c8 Apr 21, 2017
nickva pushed a commit that referenced this pull request Apr 21, 2017
The `stale` mechanism for view queries conflates two independent
concerns:

1. Whether or not the view results should be returned from a "stable"
   set of shards; i.e., mem3:ushards. This semantic is new in 2.0,
   having originated in Cloudant code in 2011[1].

2. Whether or not the view in question should be updated prior to
   responding to the user, i.e., the pre-2.0 semantics.

Both of these concerns represent consistency/availability tradeoffs, but
they're addressing rather different aspects of that continuum. As such,
the "stale" mechanism limits flexibility.

For example, it's quite likely that a user would want to retrieve
"stale" view responses from the fastest available shards - the
"available/available" choice - and this choice is not available with the
existing "stale" mechanism. A similar argument could be made for the
"consistent/consistent" choice.

This patch introduces two new view API keywords - "stable" and "update"
- to address concerns #1 and #2, respectively. The semantics of the
"stale" mechanism is implemented in terms of these new keywords.

COUCHDB-3063

[1]: apache/couchdb-fabric@93923fd
nickva pushed a commit that referenced this pull request Apr 21, 2017
eiri pushed a commit that referenced this pull request Mar 27, 2018
This closes #1

COUCHDB-2619
COUCHDB-2620
iilyak pushed a commit that referenced this pull request Jun 26, 2019
iilyak added a commit that referenced this pull request Dec 11, 2019
Update API for handle_config_terminate/3
iilyak added a commit that referenced this pull request Dec 11, 2019
garrensmith pushed a commit that referenced this pull request Jul 21, 2020
Add incremental reduce on non-leaf nodes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant