Skip to content
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

Use proto encoding for scheduler workflow next time cache #5277

Merged
merged 3 commits into from
Jan 12, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 37 additions & 0 deletions api/schedule/v1/message.go-helpers.pb.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

194 changes: 153 additions & 41 deletions api/schedule/v1/message.pb.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

14 changes: 14 additions & 0 deletions proto/internal/temporal/server/api/schedule/v1/message.proto
Original file line number Diff line number Diff line change
Expand Up @@ -125,3 +125,17 @@ message TerminateWorkflowRequest {
temporal.api.common.v1.WorkflowExecution execution = 5;
string reason = 6;
}

message NextTimeCache {
// workflow logic version (invalidate when changed)
int64 version = 1;
// start time that the results were calculated from
google.protobuf.Timestamp start_time = 2;
// next_times and nominal_times are a series of timestamp pairs, encoded as a nanosecond
// offset from start_time. next_times has one value for each time in the cache.
// nominal_times may have up to the same number of values, but it may also be shorter (or
// empty), if the corresponding nominal time is equal to the next time.
repeated int64 next_times = 3;
repeated int64 nominal_times = 4;
bool completed = 5;
}
Binary file not shown.
Loading
Loading