fix(server,sdk)!: rename rerun to replay_invocations for clarity #1022
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
The current term
rerun
is confusing especially when compared with therun
method.Example 1:
Example 2:
The code difference between Example 1 and 2 is minimal but the impact on the graph's data is immense. Example 2 will go through all previous
runs
/invocations
and will execute them again but on the latest version of the graph.What
We are renaming
rerun
toreplay_invocation
in the SDK and in the server to remove any possible confusion.Testing
The test_graph_update.py tests replay.
Contribution Checklist
make fmt
inpython-sdk/
.make fmt
inserver/
.