| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Remove couch_compaction_daemon and related tests too.
|
| | |
|
| |\
| |
| | |
Fix `badarg` crash on an invalid revision for individual doc update
|
| |/ |
|
| | |
|
| | |
|
| |\
| |
| | |
Import IOQ from Cloudant
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
This reduces non-causal test failures between apps.
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
| |
Add the junit formatter so that Jenkins can read the elixir tests
|
| | |
|
| |
|
|
|
| |
Add the elixir test to `make check` and change the build language
in travis from erlang to elixir.
|
| |
|
|
|
| |
Creates EX_USERNAME, EX_PASSWORD and EX_COUCH_URL to manage the
elixir test setup.
|
| | |
|
| |
|
|
|
| |
This commit introduces a new option `snooze_period_ms` (measured in
milliseconds), and deprecates `snooze_period` while still supporting it
for obvious legacy reasons.
|
| |\
| |
| | |
Fix partitioned query database header version
|
| |/ |
|
| | |
|
| |\
| |
| | |
restrict _purge to server admin
|
| |/
|
|
|
|
|
| |
This restrict _purge and _purged_infos_limit to server admin
in terms of the security level required to run them.
Fixes #1799
|
| | |
|
| |
|
|
| |
This fixes inability to set keys with regex symbols in them
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
This allows us to set a maximun allowed number of documents
to be returned for a global or a partitioned view query and
_all_docs query.
Co-authored-by: Paul J. Davis <paul.joseph.davis@gmail.com>
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It has a fix to revert user socket buffer size to 8192 and also
allow setting this buffer values directly (not necessarily
via {recbuf, ...}).
Fixes #1810
Warning:
2.19.0 blacklists a series of OTP releases: 21.2, 21.2.1, 21.2.2
This is done via a runtime check of the ssl application version.
The blacklist seems valid as there is a bug which prevents data from
being delivered on TSL sockets. That could affect either CouchDB
server side (chttpd) or replication client side (ibrowse).
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Some GET responses (e.g. 304 Not Modified) should not generate
representation metadata (e.g. Content-Type) as per rfc7232.
This fix allows to process such requests without crashing process response
on a regexp over nil.
|
| | |
|
| |
|
|
|
|
|
| |
This makes the global timeout for a map/reduce and all_docs request
configurable via the config. It separates the config into global queries
and partition queries so that it is possible to make the global timeout
is for partitioned queries
|
| |
|
| |
Closes #1053
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This server admin-only endpoint forces an n-way sync of all shards
across all nodes on which they are hosted.
This can be useful for an administrator adding a new node to the
cluster, after updating _dbs so that the new node hosts an existing db
with content, to force the new node to sync all of that db's shards.
Users may want to bump their `[mem3] sync_concurrency` value to a
larger figure for the duration of the shards sync.
Closes #1807
|
| |
|
|
|
|
|
| |
This limit helps prevent users from inadvertently misusing partitions by
refusing to add documents when the size of a partition exceeds 10GiB.
Co-authored-by: Robert Newson <rnewson@apache.org>
|
| |
|
|
|
| |
This cleans up the `couch_db_updater:merge_rev_trees/7` to instead use
an accumulator argument.
|
| |
|
|
|
| |
Co-authored-by: Garren Smith <garren.smith@gmail.com>
Co-authored-by: Robert Newson <rnewson@apache.org>
|
| |
|
|
|
| |
Co-authored-by: Garren Smith <garren.smith@gmail.com>
Co-authored-by: Robert Newson <rnewson@apache.org>
|
| |
|
|
|
|
|
|
| |
Using the internal hash values for indexes was a brittle approach to
ensuring that a specific index was or was not picked. By naming the
index and design docs we can more concretely ensure that the chosen
indexes match the intent of the test while also not breaking each time
mango internals change.
|
| |
|
|
|
|
|
|
|
| |
Now that a single shard handles the entire response we can optimize work
normally done in the coordinator by moving it to the RPC worker which
then removes the need to send an extra `skip` number of rows to the
coordinator.
Co-authored-by: Robert Newson <rnewson@apache.org>
|
| |
|
|
|
|
|
|
| |
If a user specifies document ids that scope the query to a single
partition key we can automatically determine that we only need to
consuly a single shard range.
Co-authored-by: Robert Newson <rnewson@apache.org>
|
| |
|
|
|
|
|
|
|
| |
The benefit of using partitioned databases is that views can then be
scoped to a single shard range. This allows for views to scale nearly as
linearly as document lookups.
Co-authored-by: Garren Smith <garren.smith@gmail.com>
Co-authored-by: Robert Newson <rnewson@apache.org>
|
| |
|
|
|
|
|
|
| |
This feature allows us to fetch statistics for a given partition key
which will allow for users to find bloated partitions and such forth.
Co-authored-by: Garren Smith <garren.smith@gmail.com>
Co-authored-by: Robert Newson <rnewson@apache.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This change introduces the ability for users to place a group of
documents in a single shard range by specifying a "partition key" in the
document id. A partition key is denoted by everything preceding a colon
':' in the document id.
Every document id (except for design documents) in a partitioned
database is required to have a partition key.
Co-authored-by: Garren Smith <garren.smith@gmail.com>
Co-authored-by: Robert Newson <rnewson@apache.org>
|
