-
Notifications
You must be signed in to change notification settings - Fork 559
Problems with webhdfs #50
Comments
I was trying to use webhdfs too and found a problem. In my case the problem is that webhdfs redirect to a data node every time i try to write to a file. And it seems that the redirection URL use the internal machine name of the docker image (something like a65ec753065c). Any idea about this? The following is an example request:
|
I am having the same issue as above, will it be addressed soon? |
I also have the same problem, already tried all python libraries available. |
Not sure how this would translate if using docker-compose but can get this to work using: |
@PhilipMourdjis if you're using docker-compose you can put hostname localhost like this:
|
Just follow the redirect message Location |
Notice:Step 2: Submit another HTTP PUT request using the URL in the Location header (or the returned response in case you specified noredirect) with the file data to be written. |
So far I was not able to use webhdfs with docker version of hadoop [on Ubuntu]. Here is what I tried:
For which I get
I tried using 3 different python libraries for webhdfs, but none work either. All of them stop with message similar to
when trying to create a file or folder.
I also tried rebuilding the docker image to account for port 9000 not exposed, but that did seem to help.
Am I doing something utterly wrong? I expect this to be likely given that I am a total had00p n00b :)
The text was updated successfully, but these errors were encountered: