Fixed InplaceUpdateRequirement in the distributed executions
#467
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #467 +/- ##
==========================================
- Coverage 70.15% 70.14% -0.01%
==========================================
Files 84 84
Lines 10600 10605 +5
Branches 2509 2512 +3
==========================================
+ Hits 7436 7439 +3
- Misses 2705 2712 +7
+ Partials 459 454 -5 ☔ View full report in Codecov by Sentry. |
GlassOfWhiskey
force-pushed
the
master
branch
2 times, most recently
from
9660fdc to
90a078e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This commit invalidates the instances of a data in the StreamFlow filesystem, when a step has a
InplaceUpdateRequirement.The valid data is only the data present in the location of the step which execute the inplace update, thus all the other data instances in other locations must be invalidated.
Invalidation is necessary because the old data in another location should not be used by next steps.