| 1 | # 2.1.0 (2018-02-20)
|
| 2 |
|
| 3 | - [NEW] Added API for upcoming IBM Cloud Identity and Access Management support
|
| 4 | for Cloudant on IBM Cloud. Note: IAM API key support is not yet enabled in the
|
| 5 | service.
|
| 6 | - [IMPROVED] Enhanced resilience of backup and restore processes by enabling the
|
| 7 | nodejs-cloudant retry plugin.
|
| 8 | - [IMPROVED] Added URL validation for presence of host and database elements.
|
| 9 | - [UPGRADED] Increased nodejs-cloudant dependency to 2.x.
|
| 10 |
|
| 11 | # 2.0.1 (2018-01-11)
|
| 12 |
|
| 13 | - [NEW] Changed to use nodejs-cloudant for database requests.
|
| 14 | - [IMPROVED] Added compression to restore process requests.
|
| 15 | - [FIXED] An unhandled `readstream.destroy is not a function` error when trying
|
| 16 | to terminate a restore process that encountered an error.
|
| 17 | - [UPGRADED] Increased debug dependency to 3.0.x.
|
| 18 |
|
| 19 | # 2.0.0 (2017-07-04)
|
| 20 |
|
| 21 | - [NEW] Moved to https://github.com/cloudant/couchbackup repository.
|
| 22 | - [NEW] Validate backup/restore options.
|
| 23 | - [NEW] Add User-Agent header to all requests.
|
| 24 | - [NEW] Added unique CLI exit codes for known error conditions.
|
| 25 | - [NEW] API for using as library that is more Node.js-like.
|
| 26 | - [NEW] Added `changes` event for each batch spooled from the changes feed.
|
| 27 | - [BREAKING CHANGE] The --buffer option is now --buffer-size.
|
| 28 | - [BREAKING CHANGE] The `writeerror` event is now just `error`.
|
| 29 | - [BREAKING CHANGE] The `writecomplete` event is now `finished`.
|
| 30 | - [BREAKING CHANGE] For restoring, the `written` event is now `restored`.
|
| 31 | - [REMOVED] Removed legacy 1.x API.
|
| 32 | - [IMPROVED] Verify database supports `/_bulk_get` endpoint prior to running backup.
|
| 33 | - [IMPROVED] Existence of the restore destination database is checked before
|
| 34 | starting the restore process.
|
| 35 | - [IMPROVED] Added compression for backup HTTP responses, where supported by the
|
| 36 | server.
|
| 37 | - [IMPROVED] Added HTTP persistent connection pools corresponding to the backup
|
| 38 | parallelism.
|
| 39 | - [IMPROVED] Better error handling in couchrestore when remote database
|
| 40 | cannot be written to.
|
| 41 | - [IMPROVED] Validate HTTP responses when restoring a database.
|
| 42 | - [IMPROVED] Aborts backup and restore processes for known irrecoverable errors.
|
| 43 | - [IMPROVED] Retry restore batches on transient errors.
|
| 44 | - [FIXED] An issue where the process could exit before the backup content was
|
| 45 | completely flushed to the destination stream.
|
| 46 | - [FIXED] An issue where back pressure on the output stream was ignored
|
| 47 | potentially resulting in the backup process running out of memory.
|
| 48 | - [FIXED] An issue where the log entry could be written for a batch before the
|
| 49 | batch was written to the backup file.
|
| 50 | - [FIXED] An issue where a restore of a resumed backup might not complete due to
|
| 51 | incomplete JSON entries in the backup file.
|
| 52 | - [FIXED] An issue where an empty batch could be written to the backup file.
|
| 53 | - [FIXED] An issue where the restore-time buffer size was ignored.
|
| 54 | - [FIXED] Ensure body 'rows' key exists before performing shallow backup.
|
| 55 | - [FIXED] An issue where write errors were not correctly reported.
|
| 56 | - [FIXED] An issue where couchbackup would attempt to write to an
|
| 57 | invalid output file.
|