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
Split lease task queue API into 2 #2269
Conversation
review #2262 first |
1ecafb3
to
4f5d063
Compare
* Split matching persistence LeaseTaskQueue API into * CreateTaskQueue * GetTaskQueue * Add new task queue UT * Add new task queue task UT * Deprecate legacy matching task tests
4f5d063
to
0943871
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.
This PR include changes from 2263, should I hold on reviewing this until 2263 is landed?
@@ -67,6 +67,10 @@ import ( | |||
"go.temporal.io/server/service/history/tasks" | |||
) | |||
|
|||
// TimePrecision is needed to account for database timestamp precision. | |||
// Cassandra only provides milliseconds timestamp precision, so we need to use tolerance when doing comparison | |||
const TimePrecision = 2 * time.Millisecond |
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.
this is not used anywhere in this PR?
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.
it is used by existing persistence tests, simply moving the definition from file to be deleted to here
taskQueue := &taskqueuepb.TaskQueue{Name: tl} | ||
taskQueue := &taskqueuepb.TaskQueue{ | ||
Name: tl, | ||
Kind: enumspb.TASK_QUEUE_KIND_NORMAL, |
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.
the Unspecified should be treated as Normal.
What changed?
Why?
Code cleanup & test cleanup
How did you test it?
New tests
Potential risks
N/A
Is hotfix candidate?
No