[jira] [Closed] (FLINK-6592) RawLocalFileSystem created even if fs.hdfs.hadoopconf specified

["Andrey (JIRA)" <ji...@apache.org>]

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

Andrey closed FLINK-6592.
-------------------------
    Resolution: Invalid

Looks like by default new org.apache.hadoop.conf.Configuration loads defaultFS. When BucketingSink created, it overwrites properties from core-site.xml with default values. 

Solution:
* new org.apache.hadoop.conf.Configuration(false)

> RawLocalFileSystem created even if fs.hdfs.hadoopconf specified
> ---------------------------------------------------------------
>
>                 Key: FLINK-6592
>                 URL: https://issues.apache.org/jira/browse/FLINK-6592
>             Project: Flink
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: Andrey
>
> This issue affects only BucketingSink.
> Steps to reproduce:
> * configure "fs.hdfs.hadoopconf" to point to the existing directory with core-site.xml and hdfs-site.xml:
> ** core-site.xml contains valid "fs.defaultFS" entry which points to "hdfs://<some hostname>"
> * configure bucketing sink: 
> {code}
> new BucketingSink<T>("/some/path/within/defaultFS")
> {code}
> * Run the job
> * In the logs:
> {code}
> Mkdirs failed to create /some/path/within/defaultFS
> {code}
> * hdfs filesystem implementation determined based on "basePath" and its schema: 
> {code}
> new Path(basePath).getFileSystem(hadoopConf);
> {code}
> Expected:
> * BucketingSink detect filesystem type based on "org.apache.hadoop.conf.Configuration" rather than "basePath".



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)