Speaking with @wesm, it would be really helpful to have Kerberos support in our HDFS logic. This should be straightforward; I would just need to switch to hdfsBuilderConnect() in the shim.
On a side note, is there a reason we aren't using Pivotal's libhdfs3? It uses RPCs natively rather than JNI.
https://github.com/Pivotal-Data-Attic/pivotalrd-libhdfs3
Dask has Python wrappers for this.
https://github.com/dask/hdfs3
Reporter: Christopher Aycock / @chrisaycock
Assignee: Christopher Aycock / @chrisaycock
Note: This issue was originally created as ARROW-350. Please see the migration documentation for further details.
Speaking with @wesm, it would be really helpful to have Kerberos support in our HDFS logic. This should be straightforward; I would just need to switch to
hdfsBuilderConnect()in the shim.On a side note, is there a reason we aren't using Pivotal's libhdfs3? It uses RPCs natively rather than JNI.
https://github.com/Pivotal-Data-Attic/pivotalrd-libhdfs3
Dask has Python wrappers for this.
https://github.com/dask/hdfs3
Reporter: Christopher Aycock / @chrisaycock
Assignee: Christopher Aycock / @chrisaycock
Note: This issue was originally created as ARROW-350. Please see the migration documentation for further details.