-
Notifications
You must be signed in to change notification settings - Fork 74
Translate from DB to objects #19
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
Conversation
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.
Finished reviewing the db part. Moving on to the storage provider.
Offset INT, | ||
Length INT, | ||
Checkpoint TEXT, | ||
Error TEXT, |
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.
Dirk, my experience has been that persisting errors to DB never works out well, especially when there's resumption involved. Can we get rid of this and add it back only if we absolutely need it ?
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.
We have a checkpoint value called "Complete" but we don't have a way to distinguish between "Completed successfully" and "Completed with error". I'm open to suggestions here.
} | ||
|
||
// TODO: use a generic data transfer descriptor instead of a URL | ||
u := url.URL{} |
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.
Yeah, this should change to the opaque transfer descriptor byte token.
Note: This doesn't compile, as some of the changes are made in the other open PRs: #20 #21 #22 #23
I separated out the PRs to try to make it easier to review them instead of having a single giant PR.