Tony Foerster has uploaded this change for review. ( http://gerrit.cloudera.org:8080/10941
Change subject: WIP Add error handling to KuduBackup DONT_BUILD KuduBackup will attempt to backup every table. If any one table fails the entire job will fail. All exceptions are logged when they happen. ...................................................................... WIP Add error handling to KuduBackup DONT_BUILD KuduBackup will attempt to backup every table. If any one table fails the entire job will fail. All exceptions are logged when they happen. A backup attempt can have 3 results: - Success - table was backed up - Exists - table backup 'metadata' directory already existed. Assuming this was a retry. - Failure - table failed to backup. All data At the end of the job lists of failures, successes, and existing backups are printed out. A lot of this code is still assuming the 'batch' backup mode. I think a lot of this will change when we start doing the incremental backups. TODO - - if 'overwrite' flag is specified, overwrite the 'metadata' folder. Not sure yet how to handle this on retries or if it's even a good idea. Change-Id: I104fd604e12b70fcff9beace71ed4ef96b54d691 --- M java/kudu-backup/src/main/scala/org/apache/kudu/backup/KuduBackup.scala M java/kudu-backup/src/main/scala/org/apache/kudu/backup/KuduBackupOptions.scala M java/kudu-backup/src/main/scala/org/apache/kudu/backup/KuduRestore.scala M java/kudu-backup/src/test/scala/org/apache/kudu/backup/TestKuduBackup.scala 4 files changed, 208 insertions(+), 46 deletions(-) git pull ssh://gerrit.cloudera.org:29418/kudu refs/changes/41/10941/1 -- To view, visit http://gerrit.cloudera.org:8080/10941 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: kudu Gerrit-Branch: master Gerrit-MessageType: newchange Gerrit-Change-Id: I104fd604e12b70fcff9beace71ed4ef96b54d691 Gerrit-Change-Number: 10941 Gerrit-PatchSet: 1 Gerrit-Owner: Tony Foerster <[email protected]>
