| commit | d67049cca5bba6fbe484f3b55356d238ab44515b | [log] [tgz] |
|---|---|---|
| author | Benjamin Bastian <benjamin.bastian@gmail.com> | Tue Jan 19 16:29:34 2016 -0800 |
| committer | Benjamin Bastian <benjamin.bastian@gmail.com> | Thu Jan 21 11:15:35 2016 -0800 |
| tree | 5094a91102077faba4a8d2f7db12b35b0b2dd7e9 | |
| parent | 4c94f3095595a50a71860a75cc8866adb9a28ce3 [diff] |
Add owner of shard to last_seq of changes response Prior to this commit, there was a bug where the response of a changes query would include epoch information for every change, but not for the last sequence. Subsequent shard changes queries would rewind from zero if the last_seq field was used in the clustered changes query and any shard had previously been moved.
Fabric is a collection of proxy functions for CouchDB operations in a cluster. These functions are used in CouchDB as the remote procedure endpoints on each of the cluster nodes.
For example, creating a database is a straightforward task in CouchDB 1.x, but for a clustered CouchDB, each node that will store a shard for the database needs to receive and execute a fabric function. The node handling the request also needs to compile the results from each of the nodes and respond accordingly to the client.
Fabric is used in conjunction with ‘Rexi’ which is also an application within CouchDB.
Fabric requires R13B03 or higher and can be built with rebar.