Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CouchDB documents should launch into Futon when double clicked in Finder. #1

Closed
jchris opened this issue May 31, 2009 · 0 comments
Closed

Comments

@jchris
Copy link
Contributor

jchris commented May 31, 2009

that'd be neat.

@janl janl closed this as completed Mar 8, 2017
janl pushed a commit that referenced this issue Jun 3, 2017
This closes #1

COUCHDB-2619
COUCHDB-2620
michellephung pushed a commit to michellephung/couchdb that referenced this issue Jul 30, 2017
This closes apache#1

Signed-off-by: ILYA Khlopotov <[email protected]>
michellephung pushed a commit to michellephung/couchdb that referenced this issue Jul 30, 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 apache#1 and apache#2, respectively. The semantics of the
"stale" mechanism is implemented in terms of these new keywords.

COUCHDB-3063

[1]: apache/couchdb-fabric@93923fd
michellephung pushed a commit to michellephung/couchdb that referenced this issue Jul 30, 2017
lag-linaro pushed a commit to lag-linaro/couchdb that referenced this issue Oct 25, 2018
lag-linaro pushed a commit to lag-linaro/couchdb that referenced this issue Oct 25, 2018
kocolosk referenced this issue in kocolosk/couchdb May 20, 2019
curlycabbage added a commit to curlycabbage/couchdb that referenced this issue Nov 20, 2019
curlycabbage added a commit to curlycabbage/couchdb that referenced this issue Nov 21, 2019
curlycabbage added a commit to curlycabbage/couchdb that referenced this issue Nov 21, 2019
asfgit pushed a commit that referenced this issue Nov 22, 2019
Update API for handle_config_terminate/3
asfgit pushed a commit that referenced this issue Nov 22, 2019
rnewson added a commit that referenced this issue Jul 21, 2020
Add incremental reduce on non-leaf nodes.
jaydoane pushed a commit that referenced this issue Dec 25, 2020
Az162 general cleanup and improvement.
Will continue work on erlang branch.
jaydoane pushed a commit that referenced this issue Dec 25, 2020
…d-current-calls

Add check for processes by first/current call
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

No branches or pull requests

2 participants