This closes #2

Signed-off-by: Alexander Shorin <[email protected]>

Fixes issue apache#2.

This closes #2

Signed-off-by: ILYA Khlopotov <[email protected]>

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

This closes #2

Signed-off-by: ILYA Khlopotov <[email protected]>

This closes #2

Signed-off-by: ILYA Khlopotov <[email protected]>

this feature makes it easier to setup a cluster for browser
applications like fauxton as browsers follow the same-origin
policy. Before this PR you had to open the wizard in Fauxton on
all three nodes and enter your data there, which was quite
confusing and hard to explain. Now you can stay in the same tab
at the same address.

This PR enables three new params in the body:

`remote_node`:

ip of the remote node where we want to send the `enable_cluster`
request

`remote_current_user`:

the current admin username of the remote node

`remote_current_password`:

the current admin password of the remote node

To test, I run:

```
rm -rf dev/lib/ && ./dev/run --no-join --admin=a:b
```

and then run the test script:

```
./src/setup/test/t-frontend-setup.sh
```

COUCHDB-2598

PR: #2
PR-URL: apache/couchdb-setup#2
Reviewed-By: Jan Lehnardt <[email protected]>
Reviewed-By: Alexander Shorin <[email protected]>

PR: #2
PR-URL: apache/couchdb-setup#2
Reviewed-By: Jan Lehnardt <[email protected]>
Reviewed-By: Alexander Shorin <[email protected]>

PR: #2
PR-URL: apache/couchdb-setup#2
Reviewed-By: Jan Lehnardt <[email protected]>
Reviewed-By: Alexander Shorin <[email protected]>

Previous if the anonymous opening process died it would cause
dreyfus_index_manager to exit and kill all other dreyfus_index
processes. This lead to bad things happening in multiple places.

This fix just tracks the anonymous opener processs in the ?BY_PID table
so we know about it when it dies. The exit status is then reused the
same as would have been for an error returned when opening the index.

Fixes: apache#2

Avoid using `erlang:now/0`

This closes #2

Signed-off-by: Alexander Shorin <[email protected]>

Previously the auth was injected unconidtionally. There were two problems:

1. no way to specify `basic_auth` credentials
2. no way to disable injection

Due to #2 it was impossible to use other user than hardcoded `adm` ()
in `Couch.login/3`.

Previously the auth was injected unconidtionally. There were two problems:

1. no way to specify `basic_auth` credentials
2. no way to disable injection

Due to #2 it was impossible to use other user than hardcoded `adm` ()
in `Couch.login/3`.

Try to gently suggest using option apache#2

AZ166: Erlang version improvements

Add check for shard safety/liveness

This closes apache#2

Signed-off-by: Alexander Shorin <[email protected]>

git-svn-id: https://svn.apache.org/repos/asf/couchdb/branches/0.11.x@955312 13f79535-47bb-0310-9956-ffa450edef68