Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
feat: delete staging and load files post successful sync #5428
feat: delete staging and load files post successful sync #5428
Changes from 1 commit
47e7504
7757329
820720e
e83063b
25d59cb
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 368 in warehouse/router/upload.go
Codecov / codecov/patch
warehouse/router/upload.go#L368
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.
@shekhar-rudder Say if this fails. Would the job be retried? If yes, in next retry would it continue from just
cleanupObjectStorageFiles
?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.
@shekhar-rudder @achettyiitr Also from PRD doc, did we close on failing the job or considering metric and internal alert for now?
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.
@RanjeetMishra If the cleanup fails, the job will be marked as failed. On the next retry, I would assume it will proceed as it would for any other error.
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.
Since now it is config based deletion, I think its fine to mark the job as failed. If customer doesn't want the syncs to error out, they can always turn it off.
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.
Seems fine if we are aligning with marking sync jobs as failed. Regarding destination config for old and new destinations lets finalize tomorrow. This PR is good to go in that case.
Check warning on line 442 in warehouse/router/upload.go
Codecov / codecov/patch
warehouse/router/upload.go#L441-L442
Check warning on line 449 in warehouse/router/upload.go
Codecov / codecov/patch
warehouse/router/upload.go#L448-L449
Check warning on line 453 in warehouse/router/upload.go
Codecov / codecov/patch
warehouse/router/upload.go#L452-L453
Check warning on line 460 in warehouse/router/upload.go
Codecov / codecov/patch
warehouse/router/upload.go#L459-L460