Documented the need for hadoop config after insert-segment-to-db #3402
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
|
👍 @ashishawasthi do you mind filling out the CLA located at http://druid.io/community/cla.html |
|
@fjy submitted CLA |
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.
Default file-system in 'core-site.xml' is required after running insert-segment-to-db when segments are stored in HDFS, since it saves all segment paths as relative URLs.
While running insert-segment-to-db, class io.druid.storage.hdfs.HdfsDataSegmentFinder changes the absolute path to relative.
While loading the segments using relative path, io.druid.storage.hdfs.HdfsDataSegmentPuller.getSegmentFiles calls path.getFileSystem(config), which (in absence of "fs.defaultFS" in Hadoop conf, in org.apache.hadoop.fs.FileSystem) assumes it to be a file on local disc, even when type in segment metadata is set to hdfs.