-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Change default order for listClosedWorkflowExecutions to by close time #312 #555
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
Change default order for listClosedWorkflowExecutions to by close time #312 #555
Conversation
…listclosedworkflowexecutions_order
…rmanu/temporal into listclosedworkflowexecutions_order
| CREATE INDEX closed_by_status ON closed_executions (status); | ||
|
|
||
| -- same as closed_executions but order by close_time | ||
| CREATE TABLE closed_executions_v2 ( |
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.
@samarabbas @shawnhathaway - I can also remove the v2 suffix here if you think that makes sense
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.
Yea, given v1 is being removed, this would make sense. We have done this in other places.
…listclosedworkflowexecutions_order
| CREATE INDEX closed_by_status ON closed_executions (status); | ||
|
|
||
| -- same as closed_executions but order by close_time | ||
| CREATE TABLE closed_executions_v2 ( |
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.
Yea, given v1 is being removed, this would make sense. We have done this in other places.
…listclosedworkflowexecutions_order
…rmanu/temporal into listclosedworkflowexecutions_order
…listclosedworkflowexecutions_order
This PR removes:
- The option to switch between V1 and V2 Persistence Visibility stores (V1 was the default)
- The V2 Cassandra Persistence Visibility Store (merged it with the V1 store).
- The V1 tables in Cassandra itself
As a result, running tctl wf list now returns closed workflows ordered by their closed time in a descending order as mentioned in this issue: #312
Tested locally with unit tests and confirmed tctl returns in the expected order