-
Notifications
You must be signed in to change notification settings - Fork 9
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
CORE-17387 - Flow timeout events. #1272
Conversation
"doc": "Represents of a flow timeout instruction.", | ||
"fields": [ | ||
{ | ||
"name": "checkpointStateKey", |
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.
As I understand, this is the flow ID, but I thought maybe it's worth being specific in case this changes/evolves.
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.
Think there's no harm in having it.
"doc": "Key for the state record that is storing the checkpoint." | ||
}, | ||
{ | ||
"name": "timeoutDateTime", |
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 probably not strictly necessary but may be useful when troubleshooting or monitoring the system health?
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.
We're not great in general at using Avro records for this sort of thing, but it does give us a chance to log at the point where we receive the event.
Jenkins build for PR 1272 build 2 Build Successful: |
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.
LGTM
Topic and Avro schema for flow timeout events.