You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/01/07 10:41:00 UTC

[jira] [Updated] (FLINK-5409) Separate Job API from the Runtime

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

Flink Jira Bot updated FLINK-5409:
----------------------------------
      Labels: auto-deprioritized-major auto-deprioritized-minor  (was: auto-deprioritized-major stale-minor)
    Priority: Not a Priority  (was: Minor)

This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion.


> Separate Job API from the Runtime
> ---------------------------------
>
>                 Key: FLINK-5409
>                 URL: https://issues.apache.org/jira/browse/FLINK-5409
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / DataStream
>            Reporter: Matt Zimmer
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> Currently, all of the Flink runtime is visible to jobs.  It will make classpath management easier if only the minimum needed to create processing jobs is loaded in the job ClassLoader.  This would ideally be limited to the job API and jars placed in a folder designated for sharing across jobs (as /lib is now, but it contains the flink-dist_*.jar) and would exclude flink runtime support classes and jars.
> I've discussed this with [~till.rohrmann] and [~rmetzger].



--
This message was sent by Atlassian Jira
(v8.20.1#820001)