| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
By default, transactions are used to check metadata, and possibly
reopen the db, to get a current db handle. However, if a `max_age`
option is provided and db handle was checked less than `max_age`
milliseconds ago, use properties from that cached handle instead.
The main use of this feature be in pluggable authorization handlers
where it might be necessary to inspect the security doc multiple times
for the same request before a final decision is made.
`revs_limit/1` was updated as well, mainly for consistency since it is
almost identical to `get_security/1`.
|
| |\
| |
| |
| |
| | |
Integrate emilio - erang linter
Merging it on the grounds of CI pass and +1 in the original PR.
|
| |/ |
|
| |
|
|
| |
Add tests for view cleanup.
|
| |
|
|
|
| |
If a client notices that a job has failed we restart it. If a job failed
for a different design document id then we resubmit the build request.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Each registered index type can now get a signal on when to clean up
their indexes.
|
| | |
|
| |
|
|
|
|
|
| |
Functions are easier to read and process if they're defined in the order
that they are referenced.
Co-Authored-By: Nick Vatamaniuc <vatamane@apache.org>
|
| |
|
|
|
|
|
|
| |
Usually we indicate the transaction status of a Db handle by naming it
`TxDb`. This updates fabric2_index:build_indices/2 to match that
pattern.
Co-Authored-By: Nick Vatamaniuc <vatamane@apache.org>
|
| |
|
|
|
| |
The defaults commented out in `default.ini` did not match the names used
in `fabric2_index.erl`.
|
| |
|
|
|
|
| |
Previously in the the test we first set up the callback, then disabled the
indexing. By that time, there was a chance that building could have started
especially in a slower execution environment.
|
| |\
| |
| | |
Fix incorrect usage of couch_epi in mango plugin
|
| |/
|
|
|
| |
Previously we used the value returned from couch_epi apply as is.
However it returns a list of arguments passed in the same order.
|
| |
|
|
|
|
|
|
| |
This will let CI gate PRs hopefully as we now have the necessary FDB server
bits installed in Jenkins.
Eventually when we can run all the tests revert to using `make check-all-tests`
as the default.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Fix the case when a job is removed while there are subscribers waiting for it.
Most of the logic was already there except:
* Handle the case when when data decoded from subscription results could be
`not_found`, in that case we just pass that atom back as is.
* Need to notify the watch when jobs are removed or couch_jobs_notifiers would
wake up and send notification messages.
|
| |\
| |
| | |
Prototype/fdb layer mango plugin
|
| |/
|
|
|
|
| |
Implement the following extention points:
- `before_find(Req) -> {ok, Req}`
- `after_find(Req, HttpResp, KVs) -> {ok, KVs}`
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
In CouchDB < 4.x we compressed document bodies by default, so enable it
for 4.x as well.
Use the basic term_to_binary compression mechanism for:
- Document bodies
- Local document bodies
- Attachments, but only if they have not already been compressed.
|
| |\
| |
| | |
soft-deletion for database
|
| | |
| |
| |
| | |
Co-Authored-By: Paul J. Davis <paul.joseph.davis@gmail.com>
|
| |/
|
|
|
|
|
|
|
| |
Instead of automatically and immediately removing data and index in
database after a delete operation, soft-deletion allows to restore
the deleted data back to original state due to a “fat finger”or
undesired delete operation, up to defined periods, such as 48 hours.
Co-Authored-By: Paul J. Davis <paul.joseph.davis@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Enable running all chttpd tests. Some fixes needed for this to happen are:
* Some tests were not valid (checking shard maps, etc) and were deleted
* Some tests were disabled either because functionality is not implemented yet
or simply to minimize the diff between 3.x and this branch for when we have
to rebase
* Some applications used for index querying had to be started explicitly
* Mock updated to use new version of modules instead of old ones
|
| |
|
|
|
| |
It should only be allowed if explicitly configured. Previously we did not
propertly match on the database name and effectively always allowed it.
|
| |
|
|
|
|
| |
Call couch_views module instead of the old fabric:query_view also needed to
call `view_cb(complete, ...)` when using keys similar to how `all_docs_view/4`
does it.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Endpoints which are removed return a 410 response:
- _show
- _list
- _rewrite
Endpoints which will be implemented in CouchDB 4.x eventually now return a 510
response:
- _purge
- _purge_infos_limit
Endpoints which return a 2xx but are a no-op effectively:
- _compact
- _view_cleanup
|
| |
|
|
| |
Clean up unused mango_utils functions.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This uses couch_views_updater to create mango indexes in the doc update
along with the couch_views_indexer to update the indexes in the
background up to the creation versionstamp.
|
| |
|
|
| |
Removing quorum stats since they are not relevant with FDB.
|
| |
|
|
|
| |
Removes the view callback that was performed on the nodes before
sending the results back to the co-ordinator.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Adds a max value to use for encoding. This is useful when getting the
max range when encoding startkey/endkeys.
|
| |
|
|
|
|
| |
This adds the ability for couch_views to index an index in the docs
update transaction. This only happens if a design doc has the
field <<"interactive">> = true.
|
| | |
|
| |
|
|
|
|
| |
This creates a versionstamp for when an indexed was created
and build status for indexes. if the index has a creation_vs, then
couch_views_indexer will built the index to this creation versionstamp.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
Use `couch_rate` application for `couch_view`
|
| |/ |
|
