You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ouyangwulin (Jira)" <ji...@apache.org> on 2019/12/24 07:13:00 UTC
[jira] [Updated] (FLINK-15378) StreamFileSystemSink supported mutil
hdfs plugins.
[ https://issues.apache.org/jira/browse/FLINK-15378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ouyangwulin updated FLINK-15378:
--------------------------------
Description:
Request 1: FileSystem plugins not effect the default yarn dependecies.
Request 2: StreamFileSystemSink supported mutil hdfs plugins.
As Problem describe :
when I put a ' filesystem plugin to FLINK_HOME/pulgins in flink', and the clas{color:#172b4d}s '*com.filesystem.plugin.FileSystemFactoryEnhance*' implements '*FileSystemFactory*', when jm start, It will call FileSystem.initialize(configuration, PluginUtils.createPluginManagerFromRootFolder(configuration)) to load factories to map FileSystem#**{color}FS_FACTORIES, and the key is only schema. When tm/jm use local hadoop conf A , the user code use hadoop conf Bin 'filesystem plugin', Conf A and Conf B is used to different hadoop cluster. and The Jm will start failed, beacuse of the blodserver in JM will load Conf B to get filesystem. the full log add appendix.
was:
Request 1: FileSystem plugins not effect the default yarn dependecies.
Request 2: StreamFileSystemSink supported mutil hdfs plugins.
> StreamFileSystemSink supported mutil hdfs plugins.
> --------------------------------------------------
>
> Key: FLINK-15378
> URL: https://issues.apache.org/jira/browse/FLINK-15378
> Project: Flink
> Issue Type: Improvement
> Components: API / Core
> Affects Versions: 1.9.2, 1.11.0
> Reporter: ouyangwulin
> Priority: Major
> Fix For: 1.11.0
>
>
> Request 1: FileSystem plugins not effect the default yarn dependecies.
> Request 2: StreamFileSystemSink supported mutil hdfs plugins.
>
> As Problem describe :
> when I put a ' filesystem plugin to FLINK_HOME/pulgins in flink', and the clas{color:#172b4d}s '*com.filesystem.plugin.FileSystemFactoryEnhance*' implements '*FileSystemFactory*', when jm start, It will call FileSystem.initialize(configuration, PluginUtils.createPluginManagerFromRootFolder(configuration)) to load factories to map FileSystem#**{color}FS_FACTORIES, and the key is only schema. When tm/jm use local hadoop conf A , the user code use hadoop conf Bin 'filesystem plugin', Conf A and Conf B is used to different hadoop cluster. and The Jm will start failed, beacuse of the blodserver in JM will load Conf B to get filesystem. the full log add appendix.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)