-
-
Notifications
You must be signed in to change notification settings - Fork 383
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
added netloc support for hdfs URIs #168
base: develop
Are you sure you want to change the base?
Conversation
…DFS URIs which was against the URI specification
@vvaten Thank you for your pull request. It looks good to me. @menshikh-iv Might be a good idea to merge this after our HDFS integration tests are up. What do you think? |
@@ -355,6 +356,9 @@ class ParseUri(object): | |||
* file:///home/user/file | |||
* file:///home/user/file.bz2 | |||
|
|||
NOTE: hdfs://path/file does no longer work as it is against the URI |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add more information to comment (when this happens, what HDFS version affected, etc)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a generic change that affects all HDFS versions. They do support hdfs://host/path/file URI format. Using hdfs://path/file in smart_open violates this and also violates the URI specification (RFC3986) where the hostname part is always after the '://'. The correct way to refer to local content is hdfs:///path/file instead of hdfs://path/file.
Hello is there any way this can be merged ? As part of my work I was trying to read and write to hdfs and traced the bug to this |
removed the special handling of HDFS URIs which was against the URI specification