Skip to content

Releases: IBM/couchbackup

2.1.0 (2018-02-20)

20 Feb 09:31
@ricellis ricellis
2.1.0
d75a59a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
2.1.0 (2018-02-20)
  • [NEW] Added API for upcoming IBM Cloud Identity and Access Management support
    for Cloudant on IBM Cloud. Note: IAM API key support is not yet enabled in the
    service.
  • [IMPROVED] Enhanced resilience of backup and restore processes by enabling the
    nodejs-cloudant retry plugin.
  • [IMPROVED] Added URL validation for presence of host and database elements.
  • [UPGRADED] Increased nodejs-cloudant dependency to 2.x.
Assets 2
Loading

2.0.1 (2018-01-11)

11 Jan 15:41
@tomblench tomblench
2.0.1
d1f15f2
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
2.0.1 (2018-01-11)
  • [NEW] Changed to use nodejs-cloudant for database requests.
  • [IMPROVED] Added compression to restore process requests.
  • [FIXED] An unhandled readstream.destroy is not a function error when trying
    to terminate a restore process that encountered an error.
  • [UPGRADED] Increased debug dependency to 3.0.x.
Assets 2
Loading

2.0.0 (2017-07-04)

04 Jul 15:44
@ricellis ricellis
2.0.0
95b0c5a
Compare
Choose a tag to compare
2.0.0 (2017-07-04)
  • [NEW] Moved to https://github.com/cloudant/couchbackup repository.
  • [NEW] Validate backup/restore options.
  • [NEW] Add User-Agent header to all requests.
  • [NEW] Added unique CLI exit codes for known error conditions.
  • [NEW] API for using as library that is more Node.js-like.
  • [NEW] Added changes event for each batch spooled from the changes feed.
  • [BREAKING CHANGE] The --buffer option is now --buffer-size.
  • [BREAKING CHANGE] The writeerror event is now just error.
  • [BREAKING CHANGE] The writecomplete event is now finished.
  • [BREAKING CHANGE] For restoring, the written event is now restored.
  • [REMOVED] Removed legacy 1.x API.
  • [IMPROVED] Verify database supports /_bulk_get endpoint prior to running backup.
  • [IMPROVED] Existence of the restore destination database is checked before
    starting the restore process.
  • [IMPROVED] Added compression for backup HTTP responses, where supported by the
    server.
  • [IMPROVED] Added HTTP persistent connection pools corresponding to the backup
    parallelism.
  • [IMPROVED] Better error handling in couchrestore when remote database
    cannot be written to.
  • [IMPROVED] Validate HTTP responses when restoring a database.
  • [IMPROVED] Aborts backup and restore processes for known irrecoverable errors.
  • [IMPROVED] Retry restore batches on transient errors.
  • [FIXED] An issue where the process could exit before the backup content was
    completely flushed to the destination stream.
  • [FIXED] An issue where back pressure on the output stream was ignored
    potentially resulting in the backup process running out of memory.
  • [FIXED] An issue where the log entry could be written for a batch before the
    batch was written to the backup file.
  • [FIXED] An issue where a restore of a resumed backup might not complete due to
    incomplete JSON entries in the backup file.
  • [FIXED] An issue where an empty batch could be written to the backup file.
  • [FIXED] An issue where the restore-time buffer size was ignored.
  • [FIXED] Ensure body 'rows' key exists before performing shallow backup.
  • [FIXED] An issue where write errors were not correctly reported.
  • [FIXED] An issue where couchbackup would attempt to write to an
    invalid output file.
Assets 2
Loading