Resolved Path java serialization issue in HadoopGeoTiffRDD #2105
Conversation
This file contains 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
Signed-off-by: jbouffard <jbouffard@azavea.com>
jbouffard
force-pushed
the
hadoopgeotiffrdd-fix
branch
from
974718b
to
871c16f
Compare
pomadchin
changed the title
pomadchin
approved these changes
Mar 29, 2017
|
@lossyrob This is ready for review. |
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.
Currently,
HadoopGeoTiffRDDhas an issue where setting bothmaxTileSizeandnumPartitionscauses the reading to fail. This is due to a serialization problem where the default serializer cannot serialize/deserializeorg.apache.hadoop.fs.Path. To fix this problem, thePaths were converted toURIs during the transformation of the input key.This resolves #2103