Matthias Pohl created FLINK-34359:
-
Summary: "Kerberized YARN per-job on Docker test (default input)"
failed due to IllegalStateException
Key: FLINK-34359
URL: https://issues.apache.org/jira/browse/FLINK-34359
Martijn Visser created FLINK-34358:
--
Summary: flink-connector-jdbc nightly fails with "Expecting code
to raise a throwable"
Key: FLINK-34358
URL: https://issues.apache.org/jira/browse/FLINK-34358
Pro
Matthias Pohl created FLINK-34357:
-
Summary: IllegalAnnotationsException causes "PyFlink YARN per-job
on Docker test" e2e test to fail
Key: FLINK-34357
URL: https://issues.apache.org/jira/browse/FLINK-34357
> My opinion would be to follow the process by default, and to make
exceptions only if there're good reasons.
Sounds make sense, I will merge it after 1.19 branch cutting.
Thanks Xintong for the explanation! And sorry for bothering.
Best,
Rui
On Mon, Feb 5, 2024 at 1:20 PM Xintong Song wrote:
Thanks for the info.
My opinion would be to follow the process by default, and to make
exceptions only if there're good reasons. From your description, it sounds
like merging the PR in or after 1.19 doesn't really make a difference. In
that case, I'd suggest to merge it for the next release (i.e.
Hii, Few more details:
We are running GKE version 1.27.7-gke.1121002.
and using flink version 1.14.3.
Thanks!
On Mon, 5 Feb 2024 at 12:05, Lavkesh Lahngir wrote:
> Hii All,
>
> We run a Flink operator on GKE, deploying one Flink job per job manager.
> We utilize
> org.apache.flink.kubernetes.hi
lincoln lee created FLINK-34356:
---
Summary: Release Testin: Verify FLINK-33768 Support dynamic
source parallelism inference for batch jobs
Key: FLINK-34356
URL: https://issues.apache.org/jira/browse/FLINK-34356
lincoln lee created FLINK-34355:
---
Summary: Release Testing: Verify FLINK-34054 Support named
parameters for functions and procedures
Key: FLINK-34355
URL: https://issues.apache.org/jira/browse/FLINK-34355
Hii All,
We run a Flink operator on GKE, deploying one Flink job per job manager. We
utilize
org.apache.flink.kubernetes.highavailability.KubernetesHaServicesFactory
for high availability. The JobManager employs config maps for checkpointing
and leader election. If, at any point, the Kube API serv
Thanks Xintong for the reply.
They are Flink internal classes, and they are not used anymore.
So I think they don't affect users, the benefit of removing them
is to simplify Flink's code and reduce maintenance costs.
If we just merge some user-related PRs recently, I could merge
it after 1.19. Th
Hi Rui,
Quick question, would there be any downside if this PR doesn't go into
1.19? Or any user benefit from getting it into this release?
Best,
Xintong
On Sun, Feb 4, 2024 at 10:16 AM Rui Fan <1996fan...@gmail.com> wrote:
> Hi release managers,
>
> > The feature freeze of 1.19 has started
+1 (non-binding)
Best,
Yuxin
Hang Ruan 于2024年2月5日周一 11:22写道：
> +1 (non-binding)
>
> Best,
> Hang
>
> Dong Lin 于2024年2月5日周一 11:08写道：
>
> > Thanks for the FLIP.
> >
> > +1 (binding)
> >
> > Best,
> > Dong
> >
> > On Wed, Jan 31, 2024 at 11:41 AM Xuannan Su
> wrote:
> >
> > > Hi everyone,
> >
+1 (non-binding)
Best,
Hang
Dong Lin 于2024年2月5日周一 11:08写道：
> Thanks for the FLIP.
>
> +1 (binding)
>
> Best,
> Dong
>
> On Wed, Jan 31, 2024 at 11:41 AM Xuannan Su wrote:
>
> > Hi everyone,
> >
> > Thanks for all the feedback about the FLIP-331: Support
> > EndOfStreamTrigger and isOutputOnly
Thanks for the FLIP.
+1 (binding)
Best,
Dong
On Wed, Jan 31, 2024 at 11:41 AM Xuannan Su wrote:
> Hi everyone,
>
> Thanks for all the feedback about the FLIP-331: Support
> EndOfStreamTrigger and isOutputOnlyAfterEndOfStream operator attribute
> to optimize task deployment [1] [2].
>
> I'd lik
Thanks for updating the FLIP, Weijie.
I think separating the TwoInputProcessFunction according to whether the
input stream contains BroadcastStream makes sense.
I have a few more comments.
1. I'd suggest the names `TwoInputNonBroadcastStreamProcessFunction` and
`TwoInputBroadcastStreamProcessFunc
Hi Sergey,
Sorry for the typos. I meant:
Yes that is right, I am talking about the jdbc connector rc3 and Flink 1.18.
I am looking into finding a simple way to reproduce the issue, and will raise a
Jira if I can,
Kind regards, David.
From: Sergey Nuyanzin
Date: Friday, 2 February 2024 at
Hi Sergey,
Yes that is right I am talking about are talking about jdbc connector rc3 and
Flink 1.18.
I am looking into finding a simple way to reproduce it, and will raise a Jira
if I can,
Kind regards, David.
From: Sergey Nuyanzin
Date: Friday, 2 February 2024 at 19:46
To: dev@flink.apac
Zhanghao Chen created FLINK-34354:
-
Summary: Release Testing: Verify FLINK-34037 Improve Serialization
Configuration and Usage in Flink
Key: FLINK-34354
URL: https://issues.apache.org/jira/browse/FLINK-34354
xuyang created FLINK-34353:
--
Summary: A strange exception will be thrown if minibatch size is
not set while using mini-batch join
Key: FLINK-34353
URL: https://issues.apache.org/jira/browse/FLINK-34353
Proje
Hangxiang Yu created FLINK-34352:
Summary: Improve the documentation of allowNonRestoredState
Key: FLINK-34352
URL: https://issues.apache.org/jira/browse/FLINK-34352
Project: Flink
Issue Type
20 matches
Mail list logo
