guyben f9a2415954 Check that CommitLogManifest exists before deletion ... It appears that there are some possible flows where the reducer runs twice on the same key. Either because of some error in a subsequent key that makes the entire shard become ignored and retried, or possible some obscure error outside of the transaction on that key. The result however is that sometimes the reducer runs on a key that has already been deleted. We need to check for that to prevent a null pointer exception. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=166112173		2017-08-29 17:02:12 -04:00
..
BackupModule.java	Add "toTime" parameter to RestoreCommitLogsAction web form	2017-05-17 11:46:18 -04:00
BackupUtils.java	Refer to Datastore everywhere correctly by its capitalized form	2017-02-17 12:12:12 -05:00
BUILD	Check that CommitLogManifest exists before deletion	2017-08-29 17:02:12 -04:00
CommitLogCheckpointAction.java	Change @Auth to an AutoValue, and created a set of predefined Auths	2017-08-01 16:33:10 -04:00
CommitLogCheckpointStrategy.java	Refer to Datastore everywhere correctly by its capitalized form	2017-02-17 12:12:12 -05:00
DeleteOldCommitLogsAction.java	Check that CommitLogManifest exists before deletion	2017-08-29 17:02:12 -04:00
ExportCommitLogDiffAction.java	Change @Auth to an AutoValue, and created a set of predefined Auths	2017-08-01 16:33:10 -04:00
GcsDiffFileLister.java	Deal with gaps and forks in commit history	2017-05-17 11:30:36 -04:00
package-info.java	Update copyright year on all license headers	2017-02-02 16:27:22 -05:00
RestoreCommitLogsAction.java	Change @Auth to an AutoValue, and created a set of predefined Auths	2017-08-01 16:33:10 -04:00