| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
The active tasks test was failing sporadically. I realized that this was
due to batches of 1k+ which resulted in the test grabbing a copy of the
initial active task blob that had listed zero processed changes.
Reducing the size of individual batches guarnatees that we'll have set
an active task status with > 0 changes done.
|
| |\ |
|
| | |\
| | |
| | | |
Make COPY doc return only one "ok"
|
| | |/ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When set, every response is sent once fully generated on the server
side. This increases memory usage on the nodes but simplifies error
handling for the client as it eliminates the possibility that the
response will be deliberately terminated midway through due to a
timeout.
The config value can be changed at runtime without impacting any
in-flight responses.
|
| | |
| |
| |
| |
| | |
This keeps validation during tests but disables the validation during
production to avoid the overhead of collation.
|
| | |
| |
| |
| |
| |
| | |
Using lists:umerge/3 adds extra invocations of the collation algorithm
because its using `=<` semantics when ebtree collations are capable of
producing `lt, eq, gt` results.
|
| | |
| |
| |
| | |
Inner nodes of the B+Tree are now immutable so that they can be cached.
|
| | |
| |
| |
| |
| | |
This allows looking up multiple keys simultaneously which reduces the
amount of overhead due to node serialization and collation.
|
| | |
| |
| |
| |
| | |
This allows for batch insertion of keys in order to minimize node
serialization and collation costs.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This makes it compatible with CouchDB <= 3.x where we can create deleted
documents.
How to check:
```
$ http put $DB1/mydb
$ http put $DB1/mydb/foo _deleted:='true' a=b
{
"id": "foo",
"ok": true,
"rev": "1-ad7eb689fcae75e7a7edb57dc1f30939"
}
```
|
| | |
| |
| |
| |
| |
| |
| | |
Empty maps maybe useful to initialize the data in some cases but we don't want
to emit an entry in the output with just an empty map.
While at it, add some tests to check the basics.
|
| | |\
| | |
| | | |
Fix ordering of page_size based pagination for views
|
| | |/
| |
| |
| |
| | |
The pagination relied on id of the document. However for views it should use
combination of key and id.
|
| | |\
| | |
| | | |
clear jobs data in active area during removal
|
| | |/
| |
| |
| |
| |
| |
| | |
During job removal, it was not cleared from the active area so
active_tasks would mistakenly believe the job still existed. When we
try to actually open the data it is not there and not_found error
would be issued.@nickva found this issue during replication work.
|
| | |\
| | |
| | | |
Clear sensitive flag at end of public api functions
|
| | |/ |
|
| | |\
| | |
| | | |
Don't log client disconnects
|
| | | | |
|
| | |/
| |
| |
| |
| |
| |
| | |
Any error there would just be generating a case clause.
Remove the `{not_found, missing}` clause since it was accidentally matching on
the Rev string and the case was included in the `_Else` clause anyway.
|
| | |
| |
| |
| | |
Fixes the case where no writes are done for an index, the rater limiter
assumed it was a failure.
|
| | |\
| | |
| | | |
Pluggable persist_fun
|
| | |/ |
|
| | |\
| | |
| | | |
Prototype/fdb layer ebtree enhance
|
| | | | |
|
| | |/ |
|
| | |\
| | |
| | | |
fixup: Build couch_js for redhat linux
|
| | | |
| | |
| | |
| | |
| | |
| | | |
When building couch_js in RHEL, there is one error occurring with "undefined
reference to symbol '_ZTVN10__cxxabiv117__class_type_infoE@@CXXABI_1.3'".
This commit is to adjust binding library to address this issue.
|
| | |\ \
| | | |
| | | | |
Speed up ebtree test suite without losing coverage
|
| | |/ / |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/
| |
| |
| | |
add local_seq option to views
|
| | |\
| | |
| | | |
Validate the result from collate_fun
|
| | |/ |
|
| | |\
| | |
| | | |
Optionally add a key manager application as a dependency
|
| | |/ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, if a database was re-created on another node, a request with that
database might have found the previous db instance in the cache. In that case
it would have correctly reopened the db while in a transaction, but, because
the old db instance was deleted it would throw a database_does_not_exist which
was not the correct behavior.
To prevent that from happening, introduce an interactive = true|false option
when opening a database. User requests may specify that option and then when
the db is re-opened, it will allow it to automatically upgrade to the new db
instance instead returning an error.
Background processes will still get a database_doest_not_exist error if they
keep a db open which has now been re-created.
The interactive option may also be used in the future to set other transaction
parameters like timeouts and retries that might be different for interactive
requests vs background tasks.
|
| | |\
| | |
| | | |
Call collate for group equality
|
| | | | |
|
| | |\ \
| | |/
| |/| |
Clean up logs
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/ |
|
| | |\
| | |
| | | |
Prototype/fdb layer ebtree enhancements
|
| | | |
| | |
| | |
| | | |
We also redefine the internal collation api for clarity.
|
