[
https://issues.apache.org/jira/browse/BEAM-12792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484734#comment-17484734
]
Janek Bevendorff commented on BEAM-12792:
-----------------------------------------
??are they persistent failures and fail individually when you run the tests?
??????????
Yes, they are persistent, but I didn't really bother with testing everything
individually, since I'm not modifying any of the Python code anyway.
I submitted a draft PR here: [https://github.com/apache/beam/pull/16658]
Please have a look. There are still some design and life cycle issues with
this, on which I need Beam SDK expert advice.
??Formatting-wise, we are currently using lint and yapf autoformatter, configs
are available in the repo; but perhaps that disagrees with some of the rules in
the IDE that you have???
Not just my IDE, they outright violate PEP8. Formatting the Go code with tabs
is also a strange choice.
> Multiple jobs running on Flink session cluster reuse the persistent Python
> environment.
> ---------------------------------------------------------------------------------------
>
> Key: BEAM-12792
> URL: https://issues.apache.org/jira/browse/BEAM-12792
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-harness
> Affects Versions: 2.27.0, 2.28.0, 2.29.0, 2.30.0, 2.31.0
> Environment: Kubernetes 1.20 on Ubuntu 18.04.
> Reporter: Jens Wiren
> Priority: P1
> Labels: FlinkRunner, beam
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I'm running TFX pipelines on a Flink cluster using Beam in k8s. However,
> extra python packages passed to the Flink runner (or rather beam worker
> side-car) are only installed once per deployment cycle. Example:
> # Flink is deployed and is up and running
> # A TFX pipeline starts, submits a job to Flink along with a python whl of
> custom code and beam ops.
> # The beam worker installs the package and the pipeline finishes succesfully.
> # A new TFX pipeline is build where a new beam fn is introduced, the pipline
> is started and the new whl is submitted as in step 2).
> # This time, the new package is not being installed in the beam worker
> causing the job to fail due to a reference which does not exist in the beam
> worker, since it didn't install the new package.
>
> I started using Flink from beam version 2.27 and it has been an issue all the
> time.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
