[ 
https://issues.apache.org/jira/browse/FLINK-18211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17142776#comment-17142776
 ] 

Echo Lee edited comment on FLINK-18211 at 6/23/20, 10:49 AM:
-------------------------------------------------------------

We can see the BlobLibraryCacheManager#createUserCodeClassLoader method:
{code:java}
for (PermanentBlobKey key : requiredJarFiles){        
    libraryURLs[count] = blobService.getFile(jobId, key).toURI().toURL();
 }{code}
 

*requiredJarFiles* is actually pipeline.jars, So when creating a user 
classloader in taskmanager, the cached jar does not appear to be added to the 
classpath. It seems that pipeline.cached-files can't replace pipeline.jars.

What do you think [~kkl0u] and [~fly_in_gis]


was (Author: echo lee):
We can see the BlobLibraryCacheManager#createUserCodeClassLoader method:

for (PermanentBlobKey key : requiredJarFiles) {
       libraryURLs[count] = blobService.getFile(jobId, key).toURI().toURL();
}

 

requiredJarFiles is actually pipeline.jars, So when creating a user classloader 
in taskmanager, the cached jar does not appear to be added to the classpath. It 
seems that pipeline.cached-files can't replace pipeline.jars.

What do you think [~kkl0u] and [~fly_in_gis]

> Dynamic properties setting 'pipeline.jars' will be overwritten
> --------------------------------------------------------------
>
>                 Key: FLINK-18211
>                 URL: https://issues.apache.org/jira/browse/FLINK-18211
>             Project: Flink
>          Issue Type: Bug
>          Components: Client / Job Submission
>    Affects Versions: 1.10.0, 1.11.0
>            Reporter: Echo Lee
>            Assignee: Echo Lee
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.12.0
>
>
> When we submit the application through "flink run 
> -Dpipeline.jars='/user1.jar, user2.jar'..." command,  configuration will 
> include 'pipeline.jars', But ExecutionConfigAccessor#fromProgramOptions will 
> be reset this property, So the property set by the user is invalid.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to