| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Also add mrargs validation to match what master does and provide some
helpful feedback to the users.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This matches behavior on master:
https://github.com/apache/couchdb/blob/master/src/couch/src/couch_db.erl#L1373-L1387
|
| |
|
|
|
| |
Start stop config and couch_drv in `setup/0` and `teardown/1` instead of the
test function itself.
|
| | |
|
| | |
|
| |
|
|
| |
That is needed when indexing authentication dbs like `_users`.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously if a VDU was updated in the `before_doc_update/3` handlers, the Db
handle wasn't refreshed soon enough such that the `prepare_and_validate/3`
would not see the newly update VDU and would not run it.
To fix make a stale Db throws an exception which bubbles up all the way to
`fabric2_fdb:transactional/2` where the transaction is retried again with a
reopened Db.
During `reopen/1` make sure to properly transfer the `user_ctx` property to the
new handle, and also make sure `user_ctx` is removed from `db_options` to avoid
caching it in `fabric2_server`.
|
| |
|
|
|
|
| |
This mostly equivalent to the `couch_db` EPI plugin, but using fabric2 calls
and without some of the functions that are not relevant to FDB such as
on_compact/1 and others.
|
| | |
|
| |\
| |
| |
| |
| | |
cloudant/add-timeout-to-fold_docs_with_different_keys
Add timeout for 'fold_docs-with_different_keys' test
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
| |
Specifying a custom prefix allows having multiple CouchDB instances on a single
FDB cluster. This can be used for one form of multi-tenancy. It can also be
used for integration testing by creating a temporary prefix then deleting all
data in that directory when the test has finished.
|
| | |
|
| |
|
|
|
| |
This opens the max document size to the transaction limits rather than a
single 100k value.
|
| | |
|
| |
|
|
|
|
| |
If the indexing job has timed out and has been requed we need to exit
the current indexer. This ensures the errors are logged so that we can
keep an eye on failing jobs.
|
| |
|
|
|
|
| |
This adds couch_views which builds map indexes and stores them in FDB.
Co-authored-by: Paul J. Davis <paul.joseph.davis@gmail.com>
|
| |
|
|
|
| |
If a start or end key is not specified we still need to scope the range
read to the given `RangePrefix`.
|
| |
|
|
|
| |
This exposes a single place where we can check for whether a given
database or database name is a replicator or users database.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
The old test got around this by using couch_httpd_auth cache in its
tests which is fairly odd given that we run chttpd_auth_cache in
production. This fixes that mistake and upgrades chttpd_auth_cache so
that it works in the test scenario of changing the authentication_db
configuration.
|
| | |
|
| | |
|
| |
|
|
|
| |
Previously I was forgetting to keep the previous history around which
ended up limiting the revision depth to two.
|
| |
|
|
| |
Simple function change to `fabric2_db:name/1`
|
| |
|
|
|
|
| |
The existing logic around return codes and term formats is labyrinthine.
This is the result of much trial and error to get the new logic to
behave exactly the same as the previous implementation.
|
| |
|
|
|
|
| |
This adds the mapping of CouchDB start/end keys and so on to the similar
yet slightly different concepts in FoundationDB. The handlers for
`_all_dbs` and `_all_docs` have been udpated to use this new logic.
|
| |
|
|
|
| |
Neither partitioned databases or shard splitting will exist in a
FoundationDB layer.
|
| |
|
|
|
|
|
| |
RFC: https://github.com/apache/couchdb-documentation/pull/409
Main API is in the `couch_jobs` module. Additional description of internals is
in the README.md file.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This changes `chttpd_auth_cache` to use FoundationDB to back the
`_users` database including the `before_doc_update` and `after_doc_read`
features.
|
| |
|
|
| |
This was a remnant before we used a version per database.
|
| |
|
|
|
|
|
|
| |
This fixes the behavior when validating a document update that is
recreating a previously deleted document. Before this fix we were
sending a document body with `"_deleted":true` as the existing document.
However, CouchDB behavior expects the previous document passed to VDU's
to be `null` in this case.
|
| |
|
|
|
| |
The older chttpd/fabric split configured filters as one step in the
coordinator instead of within each RPC worker.
|
| |
|
|
|
|
|
|
| |
I was accidentally skipping this step around properly
serializing/deserializing attachments.
Note to self: If someon specifies attachment headers this will likely
break when we attempt to pack the value tuple here.
|
| |
|
|
|
|
|
|
|
|
| |
When uploading an attachment we hadn't yet flushed data to FoundationDB
which caused the md5 to be empty. The `new_revid` algorithm then
declared that was because it was an old style attachment and thus our
new revision would be a random number.
This fix just flushes our attachments earlier in the process of updating
a document.
|
| | |
|
| |
|
|
|
| |
This still holds all attachment data in RAM which we'll have to revisit
at some point.
|
| | |
|
| |
|
|
|
|
| |
This is not an exhaustive port of the entire chttpd API. However, this
is enough to support basic CRUD operations far enough that replication
works.
|
| | |
|
| |
|
|
|
|
|
|
| |
This provides a good bit of code coverage for the new implementation.
We'll want to expand this to include relevant tests from the previous
fabric test suite along with reading through the various other tests and
ensuring that we cover the API as deeply as is appropriate for this
layer.
|
