DPL: Introduce dangling edges context #14932
Open
+122
−132
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
Contributor
|
REQUEST FOR PRODUCTION RELEASES: This will add The following labels are available |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Renames
AnalysisContextto a more genericDanglingEdgesContext, used to decide on topology adjustment for a workflow.This context is now propagated to configuration and initialization context, so that aod-spawner and aod-index-builder can be even more generic. It also permits to delay loading of plugins to set the processing callbacks for aod-reader, aod-spawner, aod-index-builder and aod-ccdb to the adjustTopology stage that only happens on wokrflow deployment, and is itself provided by ArrowSupport plugin, potentially reducing memory usage.