[ https://issues.apache.org/jira/browse/FLINK-13993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16977045#comment-16977045 ]
Zili Chen commented on FLINK-13993: ----------------------------------- DISCLAIMER: I don't want to challenge this implementation Alternative shares: we possibly pass user classpath via YARN dynamic properties and normally ship files without adding user classpath in system classpath. When retrieved {{JobGraph}} from {{JobGraphRetriever}} we add back classpath from that dynamic properties. The same for other case we pass user classpath and exclude then from system classpath. > Using FlinkUserCodeClassLoaders to load the user class in the perjob mode > ------------------------------------------------------------------------- > > Key: FLINK-13993 > URL: https://issues.apache.org/jira/browse/FLINK-13993 > Project: Flink > Issue Type: Improvement > Components: Runtime / Coordination > Affects Versions: 1.9.0, 1.10.0 > Reporter: Guowei Ma > Assignee: Guowei Ma > Priority: Major > Labels: pull-request-available > Fix For: 1.10.0 > > Original Estimate: 30h > Time Spent: 20m > Remaining Estimate: 29h 40m > > Currently, Flink has the FlinkUserCodeClassLoader, which is using to load > user’s class. However, the user class and the system class are all loaded by > the system classloader in the perjob mode. This introduces some conflicts. > This document[1] gives a proposal that makes the FlinkUserClassLoader load > the user class in perjob mode. (disscuss with Till[2]) > > [1][https://docs.google.com/document/d/1fH2Cwrrmps5RxxvVuUdeprruvDNabEaIHPyYps28WM8/edit#heading=h.815t5dodlxh7] > [2] > [https://docs.google.com/document/d/1SUhFt1BmsGMLUYVa72SWLbNrrWzunvcjAlEm8iusvq0/edit] -- This message was sent by Atlassian Jira (v8.3.4#803005)