| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| | |
Relates to #1153 and #1176
|
|/ |
|
|
|
|
| |
This reverts commit 817b2b6f5f0883092df60c1ec8ec7ec6d6094a23.
|
|
|
|
| |
This reverts commit 89a727b625e74f40fcf612bda18421b8fc21eead.
|
|
|
|
| |
This reverts commit 6ffe0421ac524138a6b48fd010f2540631b83d16.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Function closures are fragile and attachment uploads would break if
fabric_doc_attachments is different on any of the nodes in a cluster, like it
might happen during a roling cluster upgrade.
Previously fe53e437ca5ec9d23aa1b55d7934daced157a9e3 introduced two versions of
the module one which handles function closure, other which handled message but
only in this commit messages are starting to be sent.
To avoid breakages in attachemnt uploads during the period of a rolling cluster
upgrade, make sure to upgrade to that commit first then upgrade to this change.
Issue #1394
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Unfortuantely, #1437 brought in a build bug that caused dist tarballs
to be created always using the last tag that could be found on the
tree. This lead to `master` building tarballs labelled `2.1.0`.
The new approach includes extensive comments to explain the approach,
fixes the bug, and for an encore adds -dirty if you're building a
CouchDB with local changes that aren't committed to git.
|
|
|
|
| |
Closes #1309
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes #927
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
the released tarball should have -RCx in the name, but not in the
extracted file, otherwise we can't simply rename the final artefact for
our public release.
|
|
|
|
|
|
|
|
|
|
|
| |
git-describe may have changed output formats. The previous regex doesn't
allow any trailing content, and git-describe always appends -g<SHA> unless
abbrev=0 is added.
This approach pulls out only the matching tag, leaving behind any
trailing garbage from git-describe, and as a bonus allows tagging a
commit from within a branch, and running a release directly from the
branch without needing to re-check out the tag itself.
|
|
|
|
|
|
| |
- send a readable error response from failed config set
- trust but verify admin-supplied content in separate function
- return specific error conditions for logging
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Previously on view compaction, the new index state would not carry
over the associated database update and purge sequences. As a
result, views who were compacted at least once could no longer
use the ?update_seq query option, or purge properly.
Closes #984
|
| |
|
|
|
|
|
| |
I couldn’t find a cleaner way to add _bulk_docs with
`new_edits: false`.
|
|
|
|
|
|
| |
This allows for using Mango queries for finding docs with conflicts.
Closes #1101
|
| |
|
| |
|
|
|
|
| |
Complete deletion tests with not found
|
|
|
|
|
|
|
|
|
|
|
|
| |
After the aebdbc452573f70f4e50d88af5814d0fbe936333 stemming is done separately
from merge so stem interactive option didn't take effect. That is mostly ok as
speed improvements should reduce the need for that option, but it still might
be nice to keep the option (just in case).
Also, a nice side effect is it removes an extra external function from
couch_key_tree module and simplifies the tests a bit.
Related PR: #958
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
When we delete files with context option set to `delete`,
`couch_file` respects configuration flag "enable_database_recovery"
and just renames the files in case it's set to true.
This change removes context for compaction files deleted
during database deletion to make sure we are actually
erasing them and not just renaming and leaving behind.
|
|\
| |
| | |
Fix for a function_clause crash in the couch_native_process for Erlang views
|
| | |
|
|/
|
|
| |
Crash was caused by a missing implementation of ddoc function for <<"views">> FunPath, implementation is based on FilterFun but matches return values of the erlang:put() which is called in the native Emit function and also expects ok and false when docs were not emitted.
|
|
|
|
| |
Thanks to Just Some Enterprises for donating the compute power!
|
| |
|
|
|
|
| |
Issue #1396
|
|
|
|
|
|
|
|
| |
This moves the sort check into the is_usable function for all indexes.
For map/reduce indexes it can add any constant fields e.g {a: {"$eq": 4}
to the prefix of the sort because it won't affect the actual sort but
will increase the chance that an index is selected. This is a user
experience fix to help a user if they don't add all the columns for an
index to the sort fields.
|