You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@storm.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/04/16 13:56:00 UTC

[jira] [Updated] (STORM-914) AutoHDFS should also update hdfs.config into Configuration

     [ https://issues.apache.org/jira/browse/STORM-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated STORM-914:
---------------------------------
    Labels: pull-request-available  (was: )

> AutoHDFS should also update hdfs.config into Configuration
> ----------------------------------------------------------
>
>                 Key: STORM-914
>                 URL: https://issues.apache.org/jira/browse/STORM-914
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-hdfs
>    Affects Versions: 0.10.0
>            Reporter: xiajun
>            Assignee: xiajun
>            Priority: Major
>              Labels: pull-request-available
>
> When storm user a specify hdfs cluster, he will put some config such as namenode.host into hdfs.config when submit storm topology, and when HdfsBolt create HdfsConfiguration, it will use hdfs.config update HDFSConfiguration, then HDFSBolt will visit the right hdfs cluster. But in AutoHDFS's renew and getHadoopCredentials, Configuration not for the HDFS that storm user specify, we should update all the Configuration with hdfs.config.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)