I don't think it's good idea to include some interpreters as dependencies onto zeppelin-zengine.

@jongyoul moved HDFSCommand to zeppelin-interpreter

it might be important to call this webHdfs instead of hdfs
there are significant and important differences on what is supported esp. with cloud providers

@felixcheung
HDFSCommand exists without the prefix Web since the beginning

@felixcheung Do you want me to update the docs and the code or the docs only ?

both of them if it makes sense?

@felixcheung
Renaming done.

sorry @hayssams I create another PR #2455 to use hdfs library directly. Because I think it is a little complicated to using webhdfs library and hard to do test. Maybe also lose some features, e.g. I am not sure whether webhdfs works with kerberized cluster.

Hello @jongyoul
OK got it.
However keep in mind that Webhdfs works in a kerberized env without any change to the source code. It simply needs to be executed in a JAAS context which is nothing else than a jaas.conf file passed as a parameter to the Zeppelin JVM

I see perhaps value in both web hdfs and hdfs (jar client)?

maybe add one property to allow user to choose which method to use. And HdfsNoteBookRepo can delegate the real work to WebHdfsNotebookRepo which use webhdfs and NativeHdfsNotebookRepo which use native hadoop client jar. So each implementation do its own work without affecting the other.