[
https://issues.apache.org/jira/browse/FLINK-39646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18079893#comment-18079893
]
Aleksandr Savonin edited comment on FLINK-39646 at 5/10/26 8:05 PM:
--------------------------------------------------------------------
Could someone please assign the ticket to me?
PR: [https://github.com/apache/flink-kubernetes-operator/pull/1111]
was (Author: JIRAUSER308765):
PR: [https://github.com/apache/flink-kubernetes-operator/pull/1111]
> Update flink-python-example to Flink 2.2
> ----------------------------------------
>
> Key: FLINK-39646
> URL: https://issues.apache.org/jira/browse/FLINK-39646
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Aleksandr Savonin
> Priority: Major
> Labels: pull-request-available
>
> The example in examples/flink-python-example still targets Flink 1.16 end to
> end, while the rest of the examples directory has already moved to Flink 2.2.
> As part of PR #1095, the jarURIs references were updated from 1.16.1 to 2.2.0
> across the examples, but the Python example was not updated.
> This ticket proposes updating that example so it aligns fully with the
> current flink:2.2 baseline.
> I verified the change by building the image and applying the FlinkDeployment
> on a Minikube cluster with operator helm chart 1.14.0. The job reaches STABLE
> / READY / RUNNING, and the print sink emits records continuously.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
