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

Posted to issues@flink.apache.org by "Piotr Nowojski (JIRA)" <ji...@apache.org> on 2019/07/09 08:41:00 UTC

[jira] [Assigned] (FLINK-12998) Document Plugins mechanism

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

Piotr Nowojski reassigned FLINK-12998:
--------------------------------------

    Assignee: Alex

> Document Plugins mechanism
> --------------------------
>
>                 Key: FLINK-12998
>                 URL: https://issues.apache.org/jira/browse/FLINK-12998
>             Project: Flink
>          Issue Type: Sub-task
>          Components: FileSystems
>    Affects Versions: 1.9.0
>            Reporter: Piotr Nowojski
>            Assignee: Alex
>            Priority: Blocker
>             Fix For: 1.9.0
>
>
> Plugins mechanism must be documented before the release. We should write down:
>  * benefits
>  * how to use existing FileSystem plugins
>  * how to implement an own custom FileSystem plugin
>  * potential issues of relaying on {{Thread.currentThread().getContextClassLoader()}}  (currently it's set only for {{FileSystemFactory}} class loading and {{FileSystemFactory#create()}} method call - if a {{FileSystem}} is accessing {{getContextClassLoader}} during runtime (write/reading) it will not work properly as a plugin.



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