-
Notifications
You must be signed in to change notification settings - Fork 481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make JobStore impls use the new PortabilityJob for #126 #141
Conversation
… impls for new PortabilityJob methods
…ric format to use for key-value store implementations
@@ -88,29 +86,62 @@ public void create(UUID jobId, LegacyPortabilityJob job) throws IOException { | |||
} | |||
|
|||
/** | |||
* Finds the {@link LegacyPortabilityJob} keyed by {@code jobId} in Datastore, or null if none found. | |||
* Atomically updates the {@link LegacyPortabilityJob} keyed by {@code jobId} to {@code job}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/LegacyPortabilityJob/PortabilityJob
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Entity previousEntity = transaction.get(key); | ||
if (previousEntity == null) { | ||
transaction.rollback(); | ||
throw new IOException("Could not find record for jobId " + jobId); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's do jobId: " + jobId to distinguish parameterized values or any convention to highlight for future debugging
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here and below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, done
Use consistent param name for jobId in debug statements.
No description provided.