[Issue #108]: replace hdfs FileSystem api with the unified Storage api. #110
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
… and pixels-tools (not yet tested).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
With the unified Storage interface, we can easily add different types of storage systems (e.g. S3, local fs, Ozone...) into Pixels.
In this PR, we have already implemented the HDFS storage, which internally use APIs in hadoop libraries to access HDFS.
The local file storage is still to be implemented.
For this PR, as we add a new column into the TBLS table in the metadata database, some components like pixels-presto may be not compatible with a component from the previous version.