flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guowei Ma (Jira)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-15786) Load connector code with separate classloader
Date Tue, 28 Jan 2020 11:27:00 GMT

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

Guowei Ma updated FLINK-15786:
    Labels: usability  (was: )

> Load connector code with separate classloader
> ---------------------------------------------
>                 Key: FLINK-15786
>                 URL: https://issues.apache.org/jira/browse/FLINK-15786
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Task
>            Reporter: Guowei Ma
>            Priority: Major
>              Labels: usability
> Currently, connector code can be seen as part of user code. Usually, users only need
to add the corresponding connector as a dependency and package it in the user jar. This is
convenient enough.
> However, connectors usually need to interact with external systems and often introduce
heavy dependencies, there is a high possibility of a class conflict of different connectors
or the user code of the same job. For example, every one or two weeks, we will receive issue
reports relevant with connector class conflict from our users. The problem can get worse when
users want to analyze data from different sources and write output to different sinks.
> Using separate classloader to load the different connector code could resolve the problem.

This message was sent by Atlassian Jira

View raw message