+1
On Wed, 19 Jul 2023, 04:25 ConradJam, wrote:
> +1
>
> Zhu Zhu 于2023年7月19日周三 10:53写道：
>
> > +1
> >
> > Thanks,
> > Zhu
> >
> > Jing Ge 于2023年7月18日周二 19:09写道：
> > >
> > > +1
> > >
> > > On Tue, Jul 18, 2023 at 1:05 PM Maximilian Michels
> > wrote:
> > >
> > > > +1
> > > >
> > > > On Tue, Jul
张一帆 created FLINK-32629:
---
Summary: Add support for dynamic CEP
Key: FLINK-32629
URL: https://issues.apache.org/jira/browse/FLINK-32629
Project: Flink
Issue Type: New Feature
Components: Libr
Hi Xintong,
> IIUC, you are suggesting to mark the classes with a red background as
`@Deprecated` in 1.18?
Exactly. They are not marked at the code level but suppose to be deprecated.
> - For the ManagedTable related classes, is there any FLIP explicitly that
decides to deprecate them? If not, I
Thank you, Jane.
What you said (preparing a FLIP for ManagedTable related classes, not
deprecating SourceFunctionProvider, and starting a dedicated discussion for
the missing annotations) sounds good to me.
In addition, if there's no objections from the community on marking
`StreamRecordTimestamp
First off, good discussion on these topics.
+1 on Xintong's latest proposal in this thread
On Wed, Jul 19, 2023 at 5:16 AM Xintong Song wrote:
> I went through the remaining Jira tickets with 2.0.0 fix-version and are
> not included in FLINK-3975.
>
> I skipped the 3 umbrella tickets below and
+0. I think it has to grow on me. A couple of things from my end:
- Have we evaluated if these new designs are an improvement on W3C's
Accessibility, Usability & Inclusion? [1]. It is something that the ASF
rightfully emphasises.
- "there is general consensus in the community that the Flink docume
+1
On Mon, Jul 17, 2023 at 5:29 AM Xintong Song wrote:
> +1
>
> Best,
>
> Xintong
>
>
>
> On Thu, Jul 13, 2023 at 9:05 PM Chesnay Schepler
> wrote:
>
> > Hello,
> >
> > Several REST responses contain a timestamp field of the current time
> >
> > There is no known use-case for said timestamp,
+1 Thanks for proposing this FLIP, Deepthi.
The designs on FLIP-333 [1] look fresh and modern and I feel they achieve
the goal in general.
A couple of suggestions from my side could be the following:
[a] Assuming that no changes are implemented to the Flink documentation, I
would like to see a v
Matt Wang created FLINK-32630:
-
Summary: The log level should change from info to warn/error if
job failed
Key: FLINK-32630
URL: https://issues.apache.org/jira/browse/FLINK-32630
Project: Flink
Flink is restarting daily once.
Flink version: 1.10.0
2023-07-19 12:33:52
org.apache.flink.util.FlinkRuntimeException: Exceeded checkpoint tolerable
failure threshold.
at org.apache.flink.runtime.checkpoint.CheckpointFailureManager
.handleTaskLevelCheckpointException(CheckpointFailureManager.ja
Flink version: 1.10.0
2023-07-19 12:33:52
org.apache.flink.util.FlinkRuntimeException: Exceeded checkpoint tolerable
failure threshold.
at org.apache.flink.runtime.checkpoint.CheckpointFailureManager
.handleTaskLevelCheckpointException(CheckpointFailureManager.java:87)
at org.apache.flink.r
CDC format like debezium-json and canal-json support read ROWKIND metadata.
1. Our first scenario is syncing data of operational tables into our streaming
warehouse.
All operational data in mysql should NOT be physically deleted, so we use
"is_deleted" column to do logical delete, and there sh
The overall Scala-related plan for this FLIP is to ignore the Scala API
because of FLIP-265. The CEP Java/Scala version
parity (through the PatternScalaAPICompletenessTest) requires us to touch
the Scala API, though, because we want to offer an alternative to the
deprecated API in FLink 1.x. I want
Hi Devs!
Based on our release schedule, it is about time for the next Flink K8s
Operator minor release.
There are still some minor work items to be completed this week, but I
suggest aiming for next Wednesday (July 26th) as the 1.6.0 release-cut -
RC1 date.
I am volunteering as the release manag
>
> We don't have a well-defined process for breaking behavioral changes. We
> could consider adding a new method with a different name.
Introducing a new API to make the behavioral change visible was also the
suggestion in the deprecation ML thread [1]. getEnvironmentVariables (or
even getEnviron
Hi Dong,
I have a couple of follow up questions about switching back and forth
between streaming and batching mode.
Especially around shuffle/watermark strategy, and keyed state backend.
First of all, it might not always be beneficial to switch into the batch
modes:
- Shuffle strategy
- Is so
Bhupendra Yadav created FLINK-32631:
---
Summary: FlinkSessionJob stuck in Created/Reconciling state
because of No Job found error in JobManager
Key: FLINK-32631
URL: https://issues.apache.org/jira/browse/FLINK-326
Sergey Nuyanzin created FLINK-32632:
---
Summary: Run Kubernetes test is unstable on AZP
Key: FLINK-32632
URL: https://issues.apache.org/jira/browse/FLINK-32632
Project: Flink
Issue Type: Bug
+1
On Mon, Jul 17, 2023 at 5:30 AM Xintong Song wrote:
> +1
>
> Best,
>
> Xintong
>
>
>
> On Thu, Jul 13, 2023 at 9:41 PM Chesnay Schepler
> wrote:
>
> > Hello,
> >
> > The job cancellation REST endpoint has a terminationMode query
> > parameter, which in the past could be set to either CANCEL
+1
On Wed, Jul 19, 2023 at 5:14 PM Jing Ge wrote:
> +1
>
> On Mon, Jul 17, 2023 at 5:30 AM Xintong Song
> wrote:
>
> > +1
> >
> > Best,
> >
> > Xintong
> >
> >
> >
> > On Thu, Jul 13, 2023 at 9:41 PM Chesnay Schepler
> > wrote:
> >
> > > Hello,
> > >
> > > The job cancellation REST endpoint ha
It doesn't need to be part of the Flink 2.0 release perse, but starting to
wonder if we'd get more bang for our buck if we started fresh with a v2
REST API vs. one-off cleanups of the current v1 API. @Chesnay Schepler
-- wdyt?
The v1 REST API seemed to grow naturally from its original use case of
Fang Yong created FLINK-32633:
-
Summary: Kubernetes e2e test is not stable
Key: FLINK-32633
URL: https://issues.apache.org/jira/browse/FLINK-32633
Project: Flink
Issue Type: Technical Debt
+1（binding)
Best regards,
Yuxia
- 原始邮件 -
发件人: "Guowei Ma"
收件人: "dev"
发送时间: 星期三, 2023年 7 月 19日 下午 1:54:52
主题: Re: [VOTE] FLIP-309: Support using larger checkpointing interval when
source is processing backlog
+1（binding）
Best,
Guowei
On Wed, Jul 19, 2023 at 11:18 AM Hang Ruan wrote:
Thanks Gyula for driving this release.
+1 for the timeline
Best,
Rui Fan
On Wed, Jul 19, 2023 at 11:03 PM Gyula Fóra wrote:
> Hi Devs!
>
> Based on our release schedule, it is about time for the next Flink K8s
> Operator minor release.
>
> There are still some minor work items to be completed
thank you gyula ,
for driving it.
+1(non binding)
Bests,
Samrat
On Thu, 20 Jul 2023 at 8:02 AM, Rui Fan <1996fan...@gmail.com> wrote:
> Thanks Gyula for driving this release.
>
> +1 for the timeline
>
> Best,
> Rui Fan
>
> On Wed, Jul 19, 2023 at 11:03 PM Gyula Fóra wrote:
>
> > Hi Devs!
> >
>
+1 (binding)
Thanks,
Zhu
yuxia 于2023年7月20日周四 09:23写道：
>
> +1（binding)
>
> Best regards,
> Yuxia
>
> - 原始邮件 -
> 发件人: "Guowei Ma"
> 收件人: "dev"
> 发送时间: 星期三, 2023年 7 月 19日 下午 1:54:52
> 主题: Re: [VOTE] FLIP-309: Support using larger checkpointing interval when
> source is processing backlog
+1, there’re methods offer parameter with String which allows users to migrate.
Best,
Leonard
> On Jul 18, 2023, at 9:26 PM, Jing Ge wrote:
>
> +1
>
> On Tue, Jul 18, 2023 at 1:11 PM Chesnay Schepler wrote:
>
>> Good catch; i've fixed the list.
>>
>> On 18/07/2023 12:20, Xintong Song wrote:
Hi, devs,
I would like to start a discussion on FLIP-346: Deprecate ManagedTable
related APIs[1].
These APIs were initially designed for Flink Table Store, which has
joined the Apache Incubator as a separate project called Apache
Paimon(incubating).
Since they are obsolete and not used by Paimon
+1
On Thu, Jul 20, 2023 at 12:31 PM Jane Chan wrote:
>
> Hi, devs,
>
> I would like to start a discussion on FLIP-346: Deprecate ManagedTable
> related APIs[1].
>
> These APIs were initially designed for Flink Table Store, which has
> joined the Apache Incubator as a separate project called Apach
+1
Best,
Xintong
On Thu, Jul 20, 2023 at 1:25 PM Jingsong Li wrote:
> +1
>
> On Thu, Jul 20, 2023 at 12:31 PM Jane Chan wrote:
> >
> > Hi, devs,
> >
> > I would like to start a discussion on FLIP-346: Deprecate ManagedTable
> > related APIs[1].
> >
> > These APIs were initially designed for
Jane Chan created FLINK-32634:
-
Summary: Deprecate StreamRecordTimestamp and ExistingField
Key: FLINK-32634
URL: https://issues.apache.org/jira/browse/FLINK-32634
Project: Flink
Issue Type: Sub-t
31 matches
Mail list logo
