-
Notifications
You must be signed in to change notification settings - Fork 917
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
Add an archival queue factory #3562
Conversation
5210cf3
to
e637864
Compare
6e8c94f
to
c93f864
Compare
2a28663
to
9bc7a96
Compare
c93f864
to
055eed6
Compare
9bc7a96
to
0457a6d
Compare
055eed6
to
dd30d67
Compare
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.
Looks good. 👍 Please land after addressing the comments.
dd30d67
to
698e70e
Compare
6ab08a1
to
3ecd20b
Compare
nit: archival_queue_task_executor_test.go and archival_queue_task_executor.go |
698e70e
to
274bfe0
Compare
98a3a68
to
e677f15
Compare
274bfe0
to
2918045
Compare
Fixed (in the parent branch), and also fixed for the factory in this branch. |
9ee1de8
to
84a8be9
Compare
60eacbf
to
d082323
Compare
604cc96
to
7e0a1b3
Compare
d082323
to
384a43f
Compare
What changed?
Adds an archival queue factory to create the archival queue.
Why?
I made this change to instantiate the archival queue.
How did you test it?
I added a unit test.
Potential risks
Not used in production.
Is hotfix candidate?
No.