[PP-2130] Configure celery response backend #2281
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
dbernstein
changed the title
dbernstein
force-pushed
the
PP-2091
branch
6 times, most recently
from
d82be35 to
34de779
Compare
|
I'm closing this one because it has been superceded by #2282 |
|
I'm going to close this one then @dbernstein |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR enables the result backend in celery. It should cause no change to the behavior of the system.
Motivation and Context
https://ebce-lyrasis.atlassian.net/browse/PP-2130
How Has This Been Tested?
I tested this update with my celery based axis 360 importer and reaper tasks which will follow after this one is merged.
Checklist