delta/couchdb.git, branch db-softdeletion github.com: apache/couchdb.git Support soft-deletion in chttpd level 2020-04-07T00:45:14+00:00 jiangph jiangph@cn.ibm.com 2020-04-07T00:41:26+00:00 3b0f7d5aba37db83cebb88ab994056bee5ace4e7 Co-Authored-By: Paul J. Davis <paul.joseph.davis@gmail.com> 
Co-Authored-By: Paul J. Davis <paul.joseph.davis@gmail.com>
Support soft-deletion in fabric level 2020-04-07T00:35:05+00:00 jiangph jiangph@cn.ibm.com 2020-04-07T00:35:05+00:00 356949643aca23214e3f5737e2d32c2573734ca7 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> 
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>
set DbPrefix with value allocated with erlfdb_hca 2020-03-24T06:10:31+00:00 jiangph jiangph@cn.ibm.com 2020-03-23T12:03:43+00:00 2c704acc78c4f9f7cf8bb40420be5b8c915d39b9 Previously we are using the DbName to set DbPrefix for clarity. In order to support soft-deletion while providing efficient value for DbPrefix allocation, we use value allocated with erlfdb_hca for DbPrefix. 
Previously we are using the DbName to set DbPrefix for clarity. In order
to support soft-deletion while providing efficient value for DbPrefix
allocation, we use value allocated with erlfdb_hca for DbPrefix.
add info endpoint for fdb stored views (#2706) 2020-03-23T17:43:34+00:00 Tony Sun tony.sun427@gmail.com 2020-03-23T17:43:34+00:00 f81f117033422c463d6230569973c9c70a1d2565 * add info endpoint This commit adds the info endpoint for design docs stored in fdb. 
* add info endpoint

This commit adds the info endpoint for design docs stored in fdb.
Fix couch_jobs after recent db re-creation commit 2020-03-22T19:08:46+00:00 Nick Vatamaniuc vatamane@apache.org 2020-03-22T00:00:17+00:00 3fba9ff5bea733b4c722d2bb4f924afe416f6e35 The e520294c7ee3f55c3e8cc7d528ff37a5a93c800f commit inadvertently changed the `fabric2_fdb:refresh/1` head matching to accept db instances with no names. `couch_jobs` uses those but they are not cached in fabric2_server. So here we return to the previous matching rule where contexts without names don't get refreshed from the cache. 
The e520294c7ee3f55c3e8cc7d528ff37a5a93c800f commit inadvertently
changed the `fabric2_fdb:refresh/1` head matching to accept db
instances with no names. `couch_jobs` uses those but they are not
cached in fabric2_server. So here we return to the previous matching
rule where contexts without names don't get refreshed from the cache.
Add a fabric doc fold test when db is re-created 2020-03-21T23:47:04+00:00 Nick Vatamaniuc vatamane@apache.org 2020-03-21T23:31:28+00:00 a008c6d0b5da269d519bd2a6ef3aa6e9aa22abc2 Check that on a transaction restarts `database_does_not_exist` error is thrown properly if database was re-created. Also we forgot to properly unload the mocked erlfdb module in `tx_too_old_mock_erlfdb/0` so we make sure to do that, otherwise it has a chance of messing up subsequent tests. 
Check that on a transaction restarts `database_does_not_exist` error is
thrown properly if database was re-created.

Also we forgot to properly unload the mocked erlfdb module in
`tx_too_old_mock_erlfdb/0` so we make sure to do that, otherwise it
has a chance of messing up subsequent tests.
Fix database re-creation 2020-03-21T21:52:39+00:00 Nick Vatamaniuc vatamane@apache.org 2020-03-21T03:14:48+00:00 e520294c7ee3f55c3e8cc7d528ff37a5a93c800f Previously it was possible for a database to be re-created while a `Db` handle was open and the `Db` handle would continue operating on the new db without any error. To avoid that situation ensure instance UUID is explicitly checked during open and reopen calls. This includes checking it after the metadata is loaded in `fabric2_fdb:open/2` and when fetching the handle from the cache. Also, create a `{uuid, UUID}` option to allow specifying a particular instance UUID when opening a database. If that instance doesn't exist raise a `database_does_not_exist` error. 
Previously it was possible for a database to be re-created while a `Db` handle
was open and the `Db` handle would continue operating on the new db without any
error.

To avoid that situation ensure instance UUID is explicitly checked during open
and reopen calls. This includes checking it after the metadata is loaded in
`fabric2_fdb:open/2` and when fetching the handle from the cache.

Also, create a `{uuid, UUID}` option to allow specifying a particular instance
UUID when opening a database. If that instance doesn't exist raise a
`database_does_not_exist` error.
Merge pull request #2681 from apache/prototype/fdb-layer-get-doc-spans 2020-03-18T20:18:00+00:00 Russell Branca chewbranca@apache.org 2020-03-18T20:18:00+00:00 15509f29c74a8dfca5126f39aaec28423b1f913e Add additional get_doc spans 
Add additional get_doc spans
 Add additional get_doc spans 2020-03-18T20:02:50+00:00 Russell Branca chewbranca@apache.org 2020-03-18T20:02:50+00:00 41be92bb94bc2b5bdc4070d3f48a6e27179ca154 






Reformat and simplify couch_views_indexer_test module
2020-03-17T22:19:01+00:00

Nick Vatamaniuc
vatamane@apache.org

2020-03-17T20:53:35+00:00

301db96fd7a9ab12f0fd787ee6cfeadf6c212c50

 * Use the `row/3` helper function in a few more places

 * Make a `run_query/3` function to shorten all the query calls

 * A few minor emilio suggesions (whitespace, comma issues, ...)





 * Use the `row/3` helper function in a few more places

 * Make a `run_query/3` function to shorten all the query calls

 * A few minor emilio suggesions (whitespace, comma issues, ...)