-
Notifications
You must be signed in to change notification settings - Fork 832
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
Support arbitrary history task category in SQL persistence #3489
Conversation
session_start TIMESTAMP DEFAULT '1970-01-02 00:00:01', | ||
last_heartbeat TIMESTAMP DEFAULT '1970-01-02 00:00:01', | ||
record_expiry TIMESTAMP DEFAULT '1970-01-02 00:00:01', |
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.
`and task_id >= ? ` + | ||
`and task_id < ?` |
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.
is this safe?
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.
Yes. This is the correct behavior, all range queries are [inclusive, exclusive).
Didn't discovered this bug before as the code path is never exercised.
Currently we still don't have any queue using this code path (archival queue will be the first one), but at least there're persistence tests ensuring the correct behavior.
3db2a38
to
1c6a997
Compare
What changed?
Why?
How did you test it?
Potential risks
Is hotfix candidate?