[
https://issues.apache.org/jira/browse/FLINK-30045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nico Kruber updated FLINK-30045:
--------------------------------
Description:
{{FromClasspathEntryClassInformationProvider}} is attempting to verify
(eagerly) whether the given MainClass is on the user classpath. However, it
doesn't handle cases where the main class is inside a nested jar.
We actually don't need this check at all since {{PackagedProgram}} is already
doing it while attempting to load the main class. Having this once should be
enough.
was:
{{FromClasspathEntryClassInformationProvider}} is attempting to verify
(eagerly) whether the given MainClass is on the user classpath. However, it
doesn't handle cases where the main class is inside a nested jar.
This is something you would see when using such a nested jar file with the
{{StandaloneApplicationClusterEntryPoint}}, e.g. from {{standalone-job.sh}}
We actually don't need this check at all since {{PackagedProgram}} is already
doing it while attempting to load the main class. Having this once should be
enough.
> FromClasspathEntryClassInformationProvider too eager to verify MainClass
> ------------------------------------------------------------------------
>
> Key: FLINK-30045
> URL: https://issues.apache.org/jira/browse/FLINK-30045
> Project: Flink
> Issue Type: Bug
> Components: Client / Job Submission
> Affects Versions: 1.16.0, 1.17.0
> Reporter: Nico Kruber
> Assignee: Nico Kruber
> Priority: Major
> Fix For: 1.17.0, 1.16.1
>
>
> {{FromClasspathEntryClassInformationProvider}} is attempting to verify
> (eagerly) whether the given MainClass is on the user classpath. However, it
> doesn't handle cases where the main class is inside a nested jar.
> We actually don't need this check at all since {{PackagedProgram}} is already
> doing it while attempting to load the main class. Having this once should be
> enough.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
