[
https://issues.apache.org/jira/browse/ARROW-9226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Pitrou resolved ARROW-9226.
-----------------------------------
Fix Version/s: 6.0.0
Resolution: Fixed
Issue resolved by pull request 10917
[https://github.com/apache/arrow/pull/10917]
> [Python] pyarrow.fs.HadoopFileSystem - retrieve options from core-site.xml or
> hdfs-site.xml if available
> --------------------------------------------------------------------------------------------------------
>
> Key: ARROW-9226
> URL: https://issues.apache.org/jira/browse/ARROW-9226
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++, Python
> Affects Versions: 0.17.1
> Reporter: Bruno Quinart
> Assignee: Itamar Turner-Trauring
> Priority: Minor
> Labels: hdfs, pull-request-available
> Fix For: 6.0.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> 'Legacy' pyarrow.hdfs.connect was somehow able to get the namenode info from
> the hadoop configuration files.
> The new pyarrow.fs.HadoopFileSystem requires the host to be specified.
> Inferring this info from "the environment" makes it easier to deploy
> pipelines.
> But more important, for HA namenodes it is almost impossible to know for sure
> what to specify. If a rolling restart is ongoing, the namenode is changing.
> There is no guarantee on which will be active in a HA setup.
> I tried connecting to the standby namenode. The connection gets established,
> but when writing a file an error is raised that standby namenodes are not
> allowed to write to.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
