Repository navigation
Pyramid operation preserves partitioning - #2311
Merged
lossyrob merged 2 commits intoAug 5, 2017
Merged
Conversation
Signed-off-by: Eugene Cheipesh <[email protected]>
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
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.
The main objective of this PR is to ensure that pyramid operation provides
Partitionerif one is provided. This was not the case because final operation performed anRDD.map.The related refactor is to merge pixels into target pyramid tile in the combine functions, rather than accumulating them in a list. This will any tiles that share a source partition will be resampled and merged on the map side, possibly reducing the shuffle volume.