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

Robert Metzger commented on FLINK-2037:
---------------------------------------

I'm not sure how to resolve this issue.
The problem is that the python code assumed that there is a flink-python.jar in 
the {{lib/}} folder.

Since we're packaging everything in one fat-jar, this assumption is not true. 
However the code required by the Python API is contained in the fat jar (called 
{{flink-dist.jar}}.
The easiest workaround for the issue is to submit the fat jar itself to the job 
client. But I don't think this is a feasible solution because the system should 
have loaded all the classes already ;)

I see the following approaches to resolve the issue:
* Create a flink-python.jar in {{lib/}} which contains the python stuff.
* Allow the CliFrontend to run without a valid jar file (i suspect this breaks 
a lot of code and reduces usability because we can not hint a user that the jar 
file is missing anymore).
* We do not submit Python jobs to a cluster using the client.

For now, I'll see whether the first option is easily doable.

> Unable to start Python API using ./bin/pyflink*.sh
> --------------------------------------------------
>
>                 Key: FLINK-2037
>                 URL: https://issues.apache.org/jira/browse/FLINK-2037
>             Project: Flink
>          Issue Type: Bug
>          Components: Python API
>    Affects Versions: 0.9
>            Reporter: Robert Metzger
>            Assignee: Robert Metzger
>            Priority: Critical
>
> Calling {{./bin/pyflink3.sh}} will lead to
> {code}
> ./bin/pyflink3.sh
> log4j:WARN No appenders could be found for logger 
> (org.apache.hadoop.metrics2.lib.MutableMetricsFactory).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> JAR file does not exist: 
> /home/robert/incubator-flink/build-target/bin/../lib/flink-python-0.9-SNAPSHOT.jar
> Use the help option (-h or --help) to get help on the command.
> {code}
> This is due to the script expecting a {{flink-python-0.9-SNAPSHOT.jar}} file 
> to exist in {{lib}} (its wrong anyways that the version name is included 
> here. That should be replaced by a {{*}}).
> I'll look into the issue ...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to