Priam

S3 may decide to slow down and throw an error. Best not to do s3 object check (API) if it is not required.

Update dependency

#775 Do not throw NPE when no backup is found for the requested date.

(#774) Do not throw NPE when no backup is found for the requested date.

(#766) Add metrics on CassandraConfig resource calls
(#769) Support configure/tune complex parameters in cassandra.yaml
(#770) Add Cass SNAPSHOT JMX status, snapshot version, last validated timestamp. Changes to Servlet API and new APIs.

(#765) Add metrics on CassandraConfig resource calls
(#768) Support configure/tune complex parameters in cassandra.yaml
(#771) Add Cass SNAPSHOT JMX status, snapshot version, last validated timestamp. Changes to Servlet API and new APIs.

(#761) Add new file format (SST_V2) and methods to get/parse remote locations.
(#761) Upload files from SnapshotMetaService in backup version 2.0, if enabled.
(#761) Process older SNAPSHOT_V2 at the restart of Priam.
(#767) Backup Verification for Backup 2.0.
(#767) Restore for Backup 2.0
(#767) Some API changes for Snapshot Verification
(#767) Remove deprecated code like flush hour or snapshot hour.

• (#762) Backup Verification for Backup 2.0.
• (#762) Restore for Backup 2.0
• (#762) Some API changes for Snapshot Verification
• (#762) Remove deprecated code like flush hour or snapshot hour.

• (#757) Add new file format (SST_V2) and methods to get/parse remote locations.
• (#757) Upload files from SnapshotMetaService in backup version 2.0, if enabled.
• (#757) Process older SNAPSHOT_V2 at the restart of Priam.

• Bug Fix: SnapshotMetaService can leave snapshots if there is any error.
• Bug Fix: SnapshotMetaService should continue building snapshot even if an unexpected file is found in snapshot.
• Add support for schema.cql files in snapshots
• More cleanup of IConfiguration and moving code to appropriate places.

• Bug Fix: SnapshotMetaService can leave snapshots if there is any error. This will ensure we do a cleanup of any leftover snapshots.
• Bug Fix: SnapshotMetaService should continue building snapshot even if an unexpected file is found in snapshot.
• More cleanup of IConfiguration and moving code to appropriate places.

(#747) Aggregate InstanceData in InstanceInfo. Move AWS specific properties in AwsInstanceInfo

• (#744) Aggregate InstanceData in InstanceInfo. Move AWS specific properties in AwsInstanceInfo.

(#739) BugFix: Null pointer exception while traversing filesystem.
(#737) Google java format validator addition. Use ./gradlew goJF to fix the formatting before sending PR.
(#740) Last but not least, a new logo for Priam.

• (#738) BugFix: Null pointer exception while traversing filesystem.
• (#736) Google java format validator addition. Use ./gradlew goJF to fix the formatting before sending PR.
• (#741) Last but not least, a new logo for Priam.

If Priam founds any forgotten files, it will move them to lost+found directory within that column family. This behavior is disabled by default. It can be enabled by priam.forgottenFileMoveEnabled configuration.

WARNING THIS IS A BREAKING RELEASE

New Feature

• (#731) Restores will be async in nature by default.
• (#731) Support for async snapshots via configuration - priam.async.snapshot. Similar support for async incrementals via configuration - priam.async.incremental.
• (#731) Better metrics for upload and download to/from remote file system.
• (#731) Better support for include/exclude keyspaces/columnfamilies from backup, incremental backup and restores.
• (#731) Expose priam configuration over HTTP and persist at regular interval (CRON) to local file system for automation/tooling.

Bug fix

• (#731) Metrics are incremented only once and in a central location at AbstractFileSystem.
• (#731) Remove deprecated AWS API Calls.

Breaking changes

• (#731) Removal of MBeans to collect metrics from S3FileSystem. They were unreliable and incorrect.
• (#731) Update to backup configurations :- isIncrBackupParallelEnabled, getIncrementalBkupMaxConsumers, getIncrementalBkupQueueSize. They are renamed to ensure naming consistency. Refer to wiki for more details.
• (#731) Changes to backup/restore configuration :- getSnapshotKeyspaceFilters, getSnapshotCFFilter, getIncrementalKeyspaceFilters, getIncrementalCFFilter, getRestoreKeyspaceFilter, getRestoreCFFilter. They are now centralized to ensure that we can support both include and exclude keyspaces/CF. Refer to wiki for more details.

WARNING THIS IS A BREAKING RELEASE

New Feature

• (#722) Restores will be async in nature by default.
• (#722) Support for async snapshots via configuration - priam.async.snapshot. Similar support for async incrementals via configuration - priam.async.incremental.
• (#722) Better metrics for upload and download to/from remote file system.
• (#722) Better support for include/exclude keyspaces/columnfamilies from backup, incremental backup and restores.
• (#722) Initial cut for support of "localdb" to support Backup Version 2.0.

Bug fix

• (#722) Metrics are incremented only once and in a central location at AbstractFileSystem.
• (#722) Remove deprecated AWS API Calls.

Breaking changes

• (#722) Removal of MBeans to collect metrics from S3FileSystem. They were unreliable and incorrect.
• (#722) Update to backup configurations :- isIncrBackupParallelEnabled, getIncrementalBkupMaxConsumers, getIncrementalBkupQueueSize. They are renamed to ensure naming consistency. Refer to wiki for more details.
• (#722) Changes to backup/restore configuration :- getSnapshotKeyspaceFilters, getSnapshotCFFilter, getIncrementalKeyspaceFilters, getIncrementalCFFilter, getRestoreKeyspaceFilter, getRestoreCFFilter. They are now centralized to ensure that we can support both include and exclude keyspaces/CF. Refer to wiki for more details.

(#727 ) Bug fix: If priam has an issue while uploading incrementals (when uploading in parallel), and exhaust the retries, it never tries to upload the file again.

• (#693) Bug fix: If priam has an issue while uploading incrementals (when uploading in parallel), and exhaust the retries, it never tries to upload the file again.