Re: [DISCUSS] FLIP-241: Completed Jobs Information Enhancement

[Xintong Song]

My impression of JobResultStore is more about fault tolerance and high
availability. Using it for providing information to users sounds worth
exploring. We probably need more time to think it through.

Given that it doesn't conflict with what we have proposed in this FLIP, I'd
suggest considering it as a separate thread and exclude it from the scope
of this one.

Best,

Xintong



On Thu, Jun 16, 2022 at 11:43 AM Yang Wang  wrote:

> This is a very useful feature both for finished streaming and batch jobs.
>
> Except for the WebUI & REST API improvements, I am curious whether we could
> also integrate some critical information(e.g. latest checkpoint) into the
> job result store[1].
> I am just feeling this is also somehow related with "Completed Jobs
> Information Enhancement".
> And I think the history server is not necessary for all the scenarios
> especially when users only want to check the job execution result.
>
> [1].
>
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-194%3A+Introduce+the+JobResultStore
>
>
> Best,
> Yang
>
> Xintong Song  于2022年6月15日周三 15:37写道：
>
> > Thanks Junhan,
> >
> > +1 for the proposed improvements.
> >
> > Best,
> >
> > Xintong
> >
> >
> >
> > On Wed, Jun 15, 2022 at 3:16 PM Yangze Guo  wrote:
> >
> > > Thanks for driving this, Junhan.
> > >
> > > I think it's a valuable usability improvement for both streaming and
> > > batch users. Looking forward to the community feedback.
> > >
> > > Best,
> > > Yangze Guo
> > >
> > >
> > >
> > > On Wed, Jun 15, 2022 at 3:10 PM junhan yang 
> > > wrote:
> > > >
> > > > Hi all,
> > > >
> > > > I would like to open a discussion on FLIP-241: Completed Jobs
> > Information
> > > > Enhancement.
> > > >
> > > > As far as we can tell, streaming and batch users have different
> > interests
> > > > in probing a job. As Flink grows into a unified streaming & batch
> > > processor
> > > > and is adopted by more and more batch users, the user experience of
> > > > completed job's inspection has become more and more important. After
> > > doing
> > > > several market research, there are several potential improvements
> > > spotted.
> > > >
> > > > The main purpose here is due to the involvement of WebUI & REST API
> > > > changes, which should be openly discussed and voted on as FLIPs.
> > > >
> > > > You can find more details in FLIP-241 document[1]. Looking forward to
> > > > your feedback.
> > > >
> > > > [1] https://cwiki.apache.org/confluence/x/dRD1D
> > > >
> > > > Best regards,
> > > > Junhan
> > >
> >
>

Re: [DISCUSS] Dockerimage + Helm chart only patch releases for the Kubernetes operator

[Yang Wang]

>From what I have learned from the last 1.0.0 release, I think it is not too
complicated and a big burden for flink-kubernetes-operator patch releases.
The major bottleneck might be the VOTE duration(e.g. jet lag, the weekend).
We almost need one week for the release after all the blockers are resolved.

Given that we already provide the snapshot image via github packages for
every commit, I believe it is easy for users to upgrade the operator if it
is really necessary and could not wait for the next release.


Best,
Yang

Chesnay Schepler  于2022年6月14日周二 20:46写道：

> My bad, our bylaws actually state that release votes must have a minimum
> 3 days duration.
>
> On 14/06/2022 14:46, Chesnay Schepler wrote:
> > Yes, pretty much.
> >
> > Mind you that the 72h voting duration is a recommendation by the ASF;
> > it's not a strict rule.
> > AFAICT we also haven't locked this down in our bylaws, apart from
> > requiring 3 votes.
> >
> > On 14/06/2022 14:25, Gyula Fóra wrote:
> >> I think what you are referring to is here:
> >> https://www.apache.org/legal/release-policy.html#source-packages
> >>
> >> Based on this we probably cannot simply release the docker image. We
> >> could
> >> decide to not release the maven artifacts though, but that seems to be a
> >> minor difference and probably not worth it.
> >>
> >> Gyula
> >>
> >> On Tue, Jun 14, 2022 at 2:19 PM Gyula Fóra  wrote:
> >>
> >>> Thanks Chesnay, these are exactly the questions I would like to clarify
> >>> because I don't really understand the limitations/boundaries of the
> >>> apache
> >>> release process.
> >>>
> >>> Is there a strict requirement to have a source release accompany the
> >>> docker image? I will have to look this up.
> >>>
> >>> Gyula
> >>>
> >>> On Tue, Jun 14, 2022 at 2:16 PM Chesnay Schepler 
> >>> wrote:
> >>>
>  On 14/06/2022 14:10, Gyula Fóra wrote:
> > For the operator the main logic (and the bugs) are part of the
> > operator
> > docker image and the helm charts associated with it. It would be nice
>  to be
> > able to have lightweight patch releases that only contain the docker
> > image + updated Helm chart.
> >
> > This would allow us to give users new docker image releases in a
> > short
> > period of time with reduced testing and voting overhead (these patch
> > releases could have a shorter voting period also).
>  I'm not sure if this is allowed because it sounds like you're
>  proposing
>  to release binaries without an associated source release
> 
> 
> >
>
>

Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee

[Yuan Mei]

Congrats, Jingsong!

Best,
Yuan

On Thu, Jun 16, 2022 at 11:31 AM Yang Wang  wrote:

> Congrats, Jingsong!
>
> Best,
> Yang
>
> Zakelly Lan  于2022年6月16日周四 11:16写道：
>
> > Congrats & well deserved!
> >
> > Best,
> > Zakelly
> >
> > On Thu, Jun 16, 2022 at 10:36 AM Guowei Ma  wrote:
> >
> > > Congrats, Jingsong!
> > >
> > > Best,
> > > Guowei
> > >
> > >
> > > On Thu, Jun 16, 2022 at 9:49 AM Hangxiang Yu 
> > wrote:
> > >
> > > > Congrats, Jingsong!
> > > >
> > > > Best,
> > > > Hangxiang
> > > >
> > > > On Thu, Jun 16, 2022 at 9:46 AM Aitozi  wrote:
> > > >
> > > > > Congrats, Jingsong!
> > > > >
> > > > > Best,
> > > > > Aitozi
> > > > >
> > > > > Zhuoluo Yang  于2022年6月16日周四 09:26写道：
> > > > >
> > > > > > Many congratulations to teacher Lee!
> > > > > >
> > > > > > Thanks,
> > > > > > Zhuoluo
> > > > > >
> > > > > >
> > > > > > Dian Fu  于2022年6月16日周四 08:54写道：
> > > > > >
> > > > > > > Congratulations, Jingsong!
> > > > > > >
> > > > > > > Regards,
> > > > > > > Dian
> > > > > > >
> > > > > > > On Thu, Jun 16, 2022 at 1:08 AM Yu Li 
> wrote:
> > > > > > >
> > > > > > > > Congrats, Jingsong!
> > > > > > > >
> > > > > > > > Best Regards,
> > > > > > > > Yu
> > > > > > > >
> > > > > > > >
> > > > > > > > On Wed, 15 Jun 2022 at 15:26, Sergey Nuyanzin <
> > > snuyan...@gmail.com
> > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Congratulations, Jingsong!
> > > > > > > > >
> > > > > > > > > On Wed, Jun 15, 2022 at 8:45 AM Jingsong Li <
> > > > > jingsongl...@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Thanks everyone.
> > > > > > > > > >
> > > > > > > > > > It's great to be with you in the Flink community!
> > > > > > > > > >
> > > > > > > > > > Best,
> > > > > > > > > > Jingsong
> > > > > > > > > >
> > > > > > > > > > On Wed, Jun 15, 2022 at 2:11 PM Yun Gao
> > > > > >  > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > Congratulations, Jingsong!
> > > > > > > > > > >
> > > > > > > > > > > Best,
> > > > > > > > > > > Yun Gao
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > >
> --
> > > > > > > > > > > From:Jing Zhang 
> > > > > > > > > > > Send Time:2022 Jun. 14 (Tue.) 11:05
> > > > > > > > > > > To:dev 
> > > > > > > > > > > Subject:Re: [ANNOUNCE] New Apache Flink PMC Member -
> > > Jingsong
> > > > > Lee
> > > > > > > > > > >
> > > > > > > > > > > Congratulations, Jingsong!
> > > > > > > > > > >
> > > > > > > > > > > Best,
> > > > > > > > > > > Jing Zhang
> > > > > > > > > > >
> > > > > > > > > > > Leonard Xu  于2022年6月14日周二 10:54写道：
> > > > > > > > > > >
> > > > > > > > > > > > Congratulations, Jingsong!
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Best,
> > > > > > > > > > > > Leonard
> > > > > > > > > > > >
> > > > > > > > > > > > > 2022年6月13日 下午6:52，刘首维  >
> > > 写道：
> > > > > > > > > > > > >
> > > > > > > > > > > > > Congratulations and well deserved, Jingsong!
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Best regards,
> > > > > > > > > > > > > Shouwei
> > > > > > > > > > > > >
> --原始邮件--
> > > > > > > > > > > > > 发件人:
> > > > > > > > > > > >
> >  "dev"
> > > > > > > > > > > >   <
> > > > > > > > > > luoyu...@alumni.sjtu.edu.cn
> > > > > > > > > > > > ;
> > > > > > > > > > > > > 发送时间:2022年6月13日(星期一) 晚上6:09
> > > > > > > > > > > > > 收件人:"dev" > > > > > > > dev@flink.apache.org
> > > > > > > > > > >;
> > > > > > > > > > > > >
> > > > > > > > > > > > > 主题:Re: [ANNOUNCE] New Apache Flink PMC
> Member -
> > > > > > Jingsong
> > > > > > > > Lee
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Congratulations, Jingsong!
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Best regards,
> > > > > > > > > > > > > Yuxia
> > > > > > > > > > > > >
> > > > > > > > > > > > > - 原始邮件 -
> > > > > > > > > > > > > 发件人: "Yun Tang"  > > > > > > > > > > > > 收件人: "dev"  > > > > > > > > > > > > 发送时间: 星期一, 2022年 6 月 13日 下午 6:12:24
> > > > > > > > > > > > > 主题: Re: [ANNOUNCE] New Apache Flink PMC Member -
> > > Jingsong
> > > > > Lee
> > > > > > > > > > > > >
> > > > > > > > > > > > > Congratulations, Jingsong! Well deserved.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Best
> > > > > > > > > > > > > Yun Tang
> > > > > > > > > > > > > 
> > > > > > > > > > > > > From: Xingbo Huang  > > > > > > > > > > > > Sent: Monday, June 13, 2022 17:39
> > > > > > > > > > > > > To: dev  > > > > > > > > > > > > Subject: Re: [ANNOUNCE] New Apache Flink PMC
> Member -
> > > > > > Jingsong
> > > > > > > > Lee
> > > > > > > > > > > > >
> > > > > > > > > > > > > Congratulations, Jingsong!
> > > > > > > > > > > > >
> > > > > > > > > > > > > Best,
> > > > > > > > > > > > > Xingbo
> > > > > > > > 

Re: [DISCUSS] FLIP-241: Completed Jobs Information Enhancement

[Yang Wang]

This is a very useful feature both for finished streaming and batch jobs.

Except for the WebUI & REST API improvements, I am curious whether we could
also integrate some critical information(e.g. latest checkpoint) into the
job result store[1].
I am just feeling this is also somehow related with "Completed Jobs
Information Enhancement".
And I think the history server is not necessary for all the scenarios
especially when users only want to check the job execution result.

[1].
https://cwiki.apache.org/confluence/display/FLINK/FLIP-194%3A+Introduce+the+JobResultStore


Best,
Yang

Xintong Song  于2022年6月15日周三 15:37写道：

> Thanks Junhan,
>
> +1 for the proposed improvements.
>
> Best,
>
> Xintong
>
>
>
> On Wed, Jun 15, 2022 at 3:16 PM Yangze Guo  wrote:
>
> > Thanks for driving this, Junhan.
> >
> > I think it's a valuable usability improvement for both streaming and
> > batch users. Looking forward to the community feedback.
> >
> > Best,
> > Yangze Guo
> >
> >
> >
> > On Wed, Jun 15, 2022 at 3:10 PM junhan yang 
> > wrote:
> > >
> > > Hi all,
> > >
> > > I would like to open a discussion on FLIP-241: Completed Jobs
> Information
> > > Enhancement.
> > >
> > > As far as we can tell, streaming and batch users have different
> interests
> > > in probing a job. As Flink grows into a unified streaming & batch
> > processor
> > > and is adopted by more and more batch users, the user experience of
> > > completed job's inspection has become more and more important. After
> > doing
> > > several market research, there are several potential improvements
> > spotted.
> > >
> > > The main purpose here is due to the involvement of WebUI & REST API
> > > changes, which should be openly discussed and voted on as FLIPs.
> > >
> > > You can find more details in FLIP-241 document[1]. Looking forward to
> > > your feedback.
> > >
> > > [1] https://cwiki.apache.org/confluence/x/dRD1D
> > >
> > > Best regards,
> > > Junhan
> >
>

[jira] [Created] (FLINK-28087) FlinkDeployment name validation

[Fred k (Jira)]

Fred k created FLINK-28087:
--

 Summary: FlinkDeployment name validation
 Key: FLINK-28087
 URL: https://issues.apache.org/jira/browse/FLINK-28087
 Project: Flink
  Issue Type: Improvement
  Components: Kubernetes Operator
Reporter: Fred k
 Fix For: kubernetes-operator-1.1.0


The FlinkDeployment CR meta.name must be match the regex:
{code:java}
 '[a-z]([-a-z0-9]*[a-z0-9])?'{code}
By RRC-1035, a DNS-1035 label must consist of lower case alphanumeric 
characters or '-', start with an alphabetic character, and end with an 
alphanumeric character (e.g. 'my-name',  or 'abc-123', regex used for 
validation is '[a-z]([-a-z0-9]*[a-z0-9])?').

The rest service name of Flink Cluster uses the meta.name of FlinkDeployment, 
So meta.name value must follow the convention of DNS-1035 label.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee

[Yang Wang]

Congrats, Jingsong!

Best,
Yang

Zakelly Lan  于2022年6月16日周四 11:16写道：

> Congrats & well deserved!
>
> Best,
> Zakelly
>
> On Thu, Jun 16, 2022 at 10:36 AM Guowei Ma  wrote:
>
> > Congrats, Jingsong!
> >
> > Best,
> > Guowei
> >
> >
> > On Thu, Jun 16, 2022 at 9:49 AM Hangxiang Yu 
> wrote:
> >
> > > Congrats, Jingsong!
> > >
> > > Best,
> > > Hangxiang
> > >
> > > On Thu, Jun 16, 2022 at 9:46 AM Aitozi  wrote:
> > >
> > > > Congrats, Jingsong!
> > > >
> > > > Best,
> > > > Aitozi
> > > >
> > > > Zhuoluo Yang  于2022年6月16日周四 09:26写道：
> > > >
> > > > > Many congratulations to teacher Lee!
> > > > >
> > > > > Thanks,
> > > > > Zhuoluo
> > > > >
> > > > >
> > > > > Dian Fu  于2022年6月16日周四 08:54写道：
> > > > >
> > > > > > Congratulations, Jingsong!
> > > > > >
> > > > > > Regards,
> > > > > > Dian
> > > > > >
> > > > > > On Thu, Jun 16, 2022 at 1:08 AM Yu Li  wrote:
> > > > > >
> > > > > > > Congrats, Jingsong!
> > > > > > >
> > > > > > > Best Regards,
> > > > > > > Yu
> > > > > > >
> > > > > > >
> > > > > > > On Wed, 15 Jun 2022 at 15:26, Sergey Nuyanzin <
> > snuyan...@gmail.com
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > > Congratulations, Jingsong!
> > > > > > > >
> > > > > > > > On Wed, Jun 15, 2022 at 8:45 AM Jingsong Li <
> > > > jingsongl...@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Thanks everyone.
> > > > > > > > >
> > > > > > > > > It's great to be with you in the Flink community!
> > > > > > > > >
> > > > > > > > > Best,
> > > > > > > > > Jingsong
> > > > > > > > >
> > > > > > > > > On Wed, Jun 15, 2022 at 2:11 PM Yun Gao
> > > > >  > > > > > >
> > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > Congratulations, Jingsong!
> > > > > > > > > >
> > > > > > > > > > Best,
> > > > > > > > > > Yun Gao
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > --
> > > > > > > > > > From:Jing Zhang 
> > > > > > > > > > Send Time:2022 Jun. 14 (Tue.) 11:05
> > > > > > > > > > To:dev 
> > > > > > > > > > Subject:Re: [ANNOUNCE] New Apache Flink PMC Member -
> > Jingsong
> > > > Lee
> > > > > > > > > >
> > > > > > > > > > Congratulations, Jingsong!
> > > > > > > > > >
> > > > > > > > > > Best,
> > > > > > > > > > Jing Zhang
> > > > > > > > > >
> > > > > > > > > > Leonard Xu  于2022年6月14日周二 10:54写道：
> > > > > > > > > >
> > > > > > > > > > > Congratulations, Jingsong!
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Best,
> > > > > > > > > > > Leonard
> > > > > > > > > > >
> > > > > > > > > > > > 2022年6月13日 下午6:52，刘首维 
> > 写道：
> > > > > > > > > > > >
> > > > > > > > > > > > Congratulations and well deserved, Jingsong!
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Best regards,
> > > > > > > > > > > > Shouwei
> > > > > > > > > > > > --原始邮件--
> > > > > > > > > > > > 发件人:
> > > > > > > > > > >
>  "dev"
> > > > > > > > > > >   <
> > > > > > > > > luoyu...@alumni.sjtu.edu.cn
> > > > > > > > > > > ;
> > > > > > > > > > > > 发送时间:2022年6月13日(星期一) 晚上6:09
> > > > > > > > > > > > 收件人:"dev" > > > > > > dev@flink.apache.org
> > > > > > > > > >;
> > > > > > > > > > > >
> > > > > > > > > > > > 主题:Re: [ANNOUNCE] New Apache Flink PMC Member -
> > > > > Jingsong
> > > > > > > Lee
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Congratulations, Jingsong!
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Best regards,
> > > > > > > > > > > > Yuxia
> > > > > > > > > > > >
> > > > > > > > > > > > - 原始邮件 -
> > > > > > > > > > > > 发件人: "Yun Tang"  > > > > > > > > > > > 收件人: "dev"  > > > > > > > > > > > 发送时间: 星期一, 2022年 6 月 13日 下午 6:12:24
> > > > > > > > > > > > 主题: Re: [ANNOUNCE] New Apache Flink PMC Member -
> > Jingsong
> > > > Lee
> > > > > > > > > > > >
> > > > > > > > > > > > Congratulations, Jingsong! Well deserved.
> > > > > > > > > > > >
> > > > > > > > > > > > Best
> > > > > > > > > > > > Yun Tang
> > > > > > > > > > > > 
> > > > > > > > > > > > From: Xingbo Huang  > > > > > > > > > > > Sent: Monday, June 13, 2022 17:39
> > > > > > > > > > > > To: dev  > > > > > > > > > > > Subject: Re: [ANNOUNCE] New Apache Flink PMC Member -
> > > > > Jingsong
> > > > > > > Lee
> > > > > > > > > > > >
> > > > > > > > > > > > Congratulations, Jingsong!
> > > > > > > > > > > >
> > > > > > > > > > > > Best,
> > > > > > > > > > > > Xingbo
> > > > > > > > > > > >
> > > > > > > > > > > > Jane Chan  > > > 17:23写道：
> > > > > > > > > > > >
> > > > > > > > > > > >  Congratulations, Jingsong!
> > > > > > > > > > > > 
> > > > > > > > > > > >  Best,
> > > > > > > > > > > >  Jane Chan
> > > > > > > > > > > > 
> > > > > > > > > > > >  On Mon, Jun 13, 2022 at 4:43 PM Shuo Cheng <
> > > > > > > > njucs...@gmail.com
> > > > > > > > > > >  wrote:
> > > > > > 

Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee

[Zakelly Lan]

Congrats & well deserved!

Best,
Zakelly

On Thu, Jun 16, 2022 at 10:36 AM Guowei Ma  wrote:

> Congrats, Jingsong!
>
> Best,
> Guowei
>
>
> On Thu, Jun 16, 2022 at 9:49 AM Hangxiang Yu  wrote:
>
> > Congrats, Jingsong!
> >
> > Best,
> > Hangxiang
> >
> > On Thu, Jun 16, 2022 at 9:46 AM Aitozi  wrote:
> >
> > > Congrats, Jingsong!
> > >
> > > Best,
> > > Aitozi
> > >
> > > Zhuoluo Yang  于2022年6月16日周四 09:26写道：
> > >
> > > > Many congratulations to teacher Lee!
> > > >
> > > > Thanks,
> > > > Zhuoluo
> > > >
> > > >
> > > > Dian Fu  于2022年6月16日周四 08:54写道：
> > > >
> > > > > Congratulations, Jingsong!
> > > > >
> > > > > Regards,
> > > > > Dian
> > > > >
> > > > > On Thu, Jun 16, 2022 at 1:08 AM Yu Li  wrote:
> > > > >
> > > > > > Congrats, Jingsong!
> > > > > >
> > > > > > Best Regards,
> > > > > > Yu
> > > > > >
> > > > > >
> > > > > > On Wed, 15 Jun 2022 at 15:26, Sergey Nuyanzin <
> snuyan...@gmail.com
> > >
> > > > > wrote:
> > > > > >
> > > > > > > Congratulations, Jingsong!
> > > > > > >
> > > > > > > On Wed, Jun 15, 2022 at 8:45 AM Jingsong Li <
> > > jingsongl...@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Thanks everyone.
> > > > > > > >
> > > > > > > > It's great to be with you in the Flink community!
> > > > > > > >
> > > > > > > > Best,
> > > > > > > > Jingsong
> > > > > > > >
> > > > > > > > On Wed, Jun 15, 2022 at 2:11 PM Yun Gao
> > > >  > > > > >
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > Congratulations, Jingsong!
> > > > > > > > >
> > > > > > > > > Best,
> > > > > > > > > Yun Gao
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > --
> > > > > > > > > From:Jing Zhang 
> > > > > > > > > Send Time:2022 Jun. 14 (Tue.) 11:05
> > > > > > > > > To:dev 
> > > > > > > > > Subject:Re: [ANNOUNCE] New Apache Flink PMC Member -
> Jingsong
> > > Lee
> > > > > > > > >
> > > > > > > > > Congratulations, Jingsong!
> > > > > > > > >
> > > > > > > > > Best,
> > > > > > > > > Jing Zhang
> > > > > > > > >
> > > > > > > > > Leonard Xu  于2022年6月14日周二 10:54写道：
> > > > > > > > >
> > > > > > > > > > Congratulations, Jingsong!
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Best,
> > > > > > > > > > Leonard
> > > > > > > > > >
> > > > > > > > > > > 2022年6月13日 下午6:52，刘首维 
> 写道：
> > > > > > > > > > >
> > > > > > > > > > > Congratulations and well deserved, Jingsong!
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Best regards,
> > > > > > > > > > > Shouwei
> > > > > > > > > > > --原始邮件--
> > > > > > > > > > > 发件人:
> > > > > > > > > > "dev"
> > > > > > > > > >   <
> > > > > > > > luoyu...@alumni.sjtu.edu.cn
> > > > > > > > > > ;
> > > > > > > > > > > 发送时间:2022年6月13日(星期一) 晚上6:09
> > > > > > > > > > > 收件人:"dev" > > > > > dev@flink.apache.org
> > > > > > > > >;
> > > > > > > > > > >
> > > > > > > > > > > 主题:Re: [ANNOUNCE] New Apache Flink PMC Member -
> > > > Jingsong
> > > > > > Lee
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Congratulations, Jingsong!
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Best regards,
> > > > > > > > > > > Yuxia
> > > > > > > > > > >
> > > > > > > > > > > - 原始邮件 -
> > > > > > > > > > > 发件人: "Yun Tang"  > > > > > > > > > > 收件人: "dev"  > > > > > > > > > > 发送时间: 星期一, 2022年 6 月 13日 下午 6:12:24
> > > > > > > > > > > 主题: Re: [ANNOUNCE] New Apache Flink PMC Member -
> Jingsong
> > > Lee
> > > > > > > > > > >
> > > > > > > > > > > Congratulations, Jingsong! Well deserved.
> > > > > > > > > > >
> > > > > > > > > > > Best
> > > > > > > > > > > Yun Tang
> > > > > > > > > > > 
> > > > > > > > > > > From: Xingbo Huang  > > > > > > > > > > Sent: Monday, June 13, 2022 17:39
> > > > > > > > > > > To: dev  > > > > > > > > > > Subject: Re: [ANNOUNCE] New Apache Flink PMC Member -
> > > > Jingsong
> > > > > > Lee
> > > > > > > > > > >
> > > > > > > > > > > Congratulations, Jingsong!
> > > > > > > > > > >
> > > > > > > > > > > Best,
> > > > > > > > > > > Xingbo
> > > > > > > > > > >
> > > > > > > > > > > Jane Chan  > > 17:23写道：
> > > > > > > > > > >
> > > > > > > > > > >  Congratulations, Jingsong!
> > > > > > > > > > > 
> > > > > > > > > > >  Best,
> > > > > > > > > > >  Jane Chan
> > > > > > > > > > > 
> > > > > > > > > > >  On Mon, Jun 13, 2022 at 4:43 PM Shuo Cheng <
> > > > > > > njucs...@gmail.com
> > > > > > > > > >  wrote:
> > > > > > > > > > > 
> > > > > > > > > > >   Congratulations, Jingsong!
> > > > > > > > > > >  
> > > > > > > > > > >   On 6/13/22, Paul Lam  > > >  > > > > > > > > > paullin3...@gmail.com> wrote:
> > > > > > > > > > >Congrats, Jingsong! Well deserved!
> > > > > > > > > > >   
> > > > > > > > > > >Best,
> > > > > > > > > > >Paul Lam
> > > > > > > > > 

[jira] [Created] (FLINK-28086) Table Store Catalog supports partition methods

[Jingsong Lee (Jira)]

Jingsong Lee created FLINK-28086:


 Summary: Table Store Catalog supports partition methods
 Key: FLINK-28086
 URL: https://issues.apache.org/jira/browse/FLINK-28086
 Project: Flink
  Issue Type: New Feature
  Components: Table Store
Reporter: Jingsong Lee
 Fix For: table-store-0.2.0


Table Store Catalog can support:
 * listPartitions
 * listPartitionsByFilter
 * getPartition
 * partitionExists
 * dropPartition



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Re: Contributing to Apache Flink

[Shubham Bansal]

Gentle reminder!!

On Sat, May 21, 2022 at 7:34 PM Shubham Bansal 
wrote:

> Hi Everyone,
>
> I have been looking at some starter tagged JIRA in the last couple of
> weeks.
>
> https://issues.apache.org/jira/browse/FLINK-27506
> https://issues.apache.org/jira/browse/FLINK-27508
> https://issues.apache.org/jira/browse/FLINK-27507
> https://issues.apache.org/jira/browse/FLINK-27509
>
> One of the changes is checked in, and others are in review.
> I wanted to be more involved in the code contribution process and would be
> happy to look at non-starter issues which can give me more insight into the
> codebase. Eventually wanting to move to core components over time.
>
> My Background: I have worked in backend API, Infrastructure, Cloud Storage
> and System Security for the past 6 years.
>
> I skimmed through different components on the JIRA and found the following
> to be very interesting.
>
> Runtime / Coordination
> Runtime / Queryable State
> Runtime / State Backends
> Runtime/ Task
> Stateful functions
> Table SQL / Planner
> Table SQL/ Runtime
> Table Store
> FileSystems
> Library / CEP
> Library / Graph Processing
> Runtime / Checkpointing
>
> I would be happy to start somewhere in any of the above areas or anything
> which you think would be more suitable.
>
> Please let me know.
>
> Thanks,
> Shubham
>

Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee

[Guowei Ma]

Congrats, Jingsong!

Best,
Guowei


On Thu, Jun 16, 2022 at 9:49 AM Hangxiang Yu  wrote:

> Congrats, Jingsong!
>
> Best,
> Hangxiang
>
> On Thu, Jun 16, 2022 at 9:46 AM Aitozi  wrote:
>
> > Congrats, Jingsong!
> >
> > Best,
> > Aitozi
> >
> > Zhuoluo Yang  于2022年6月16日周四 09:26写道：
> >
> > > Many congratulations to teacher Lee!
> > >
> > > Thanks,
> > > Zhuoluo
> > >
> > >
> > > Dian Fu  于2022年6月16日周四 08:54写道：
> > >
> > > > Congratulations, Jingsong!
> > > >
> > > > Regards,
> > > > Dian
> > > >
> > > > On Thu, Jun 16, 2022 at 1:08 AM Yu Li  wrote:
> > > >
> > > > > Congrats, Jingsong!
> > > > >
> > > > > Best Regards,
> > > > > Yu
> > > > >
> > > > >
> > > > > On Wed, 15 Jun 2022 at 15:26, Sergey Nuyanzin  >
> > > > wrote:
> > > > >
> > > > > > Congratulations, Jingsong!
> > > > > >
> > > > > > On Wed, Jun 15, 2022 at 8:45 AM Jingsong Li <
> > jingsongl...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Thanks everyone.
> > > > > > >
> > > > > > > It's great to be with you in the Flink community!
> > > > > > >
> > > > > > > Best,
> > > > > > > Jingsong
> > > > > > >
> > > > > > > On Wed, Jun 15, 2022 at 2:11 PM Yun Gao
> > >  > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > Congratulations, Jingsong!
> > > > > > > >
> > > > > > > > Best,
> > > > > > > > Yun Gao
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > --
> > > > > > > > From:Jing Zhang 
> > > > > > > > Send Time:2022 Jun. 14 (Tue.) 11:05
> > > > > > > > To:dev 
> > > > > > > > Subject:Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong
> > Lee
> > > > > > > >
> > > > > > > > Congratulations, Jingsong!
> > > > > > > >
> > > > > > > > Best,
> > > > > > > > Jing Zhang
> > > > > > > >
> > > > > > > > Leonard Xu  于2022年6月14日周二 10:54写道：
> > > > > > > >
> > > > > > > > > Congratulations, Jingsong!
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Best,
> > > > > > > > > Leonard
> > > > > > > > >
> > > > > > > > > > 2022年6月13日 下午6:52，刘首维  写道：
> > > > > > > > > >
> > > > > > > > > > Congratulations and well deserved, Jingsong!
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Best regards,
> > > > > > > > > > Shouwei
> > > > > > > > > > --原始邮件--
> > > > > > > > > > 发件人:
> > > > > > > > > "dev"
> > > > > > > > >   <
> > > > > > > luoyu...@alumni.sjtu.edu.cn
> > > > > > > > > ;
> > > > > > > > > > 发送时间:2022年6月13日(星期一) 晚上6:09
> > > > > > > > > > 收件人:"dev" > > > > dev@flink.apache.org
> > > > > > > >;
> > > > > > > > > >
> > > > > > > > > > 主题:Re: [ANNOUNCE] New Apache Flink PMC Member -
> > > Jingsong
> > > > > Lee
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Congratulations, Jingsong!
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Best regards,
> > > > > > > > > > Yuxia
> > > > > > > > > >
> > > > > > > > > > - 原始邮件 -
> > > > > > > > > > 发件人: "Yun Tang"  > > > > > > > > > 收件人: "dev"  > > > > > > > > > 发送时间: 星期一, 2022年 6 月 13日 下午 6:12:24
> > > > > > > > > > 主题: Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong
> > Lee
> > > > > > > > > >
> > > > > > > > > > Congratulations, Jingsong! Well deserved.
> > > > > > > > > >
> > > > > > > > > > Best
> > > > > > > > > > Yun Tang
> > > > > > > > > > 
> > > > > > > > > > From: Xingbo Huang  > > > > > > > > > Sent: Monday, June 13, 2022 17:39
> > > > > > > > > > To: dev  > > > > > > > > > Subject: Re: [ANNOUNCE] New Apache Flink PMC Member -
> > > Jingsong
> > > > > Lee
> > > > > > > > > >
> > > > > > > > > > Congratulations, Jingsong!
> > > > > > > > > >
> > > > > > > > > > Best,
> > > > > > > > > > Xingbo
> > > > > > > > > >
> > > > > > > > > > Jane Chan  > 17:23写道：
> > > > > > > > > >
> > > > > > > > > >  Congratulations, Jingsong!
> > > > > > > > > > 
> > > > > > > > > >  Best,
> > > > > > > > > >  Jane Chan
> > > > > > > > > > 
> > > > > > > > > >  On Mon, Jun 13, 2022 at 4:43 PM Shuo Cheng <
> > > > > > njucs...@gmail.com
> > > > > > > > >  wrote:
> > > > > > > > > > 
> > > > > > > > > >   Congratulations, Jingsong!
> > > > > > > > > >  
> > > > > > > > > >   On 6/13/22, Paul Lam  > >  > > > > > > > > paullin3...@gmail.com> wrote:
> > > > > > > > > >Congrats, Jingsong! Well deserved!
> > > > > > > > > >   
> > > > > > > > > >Best,
> > > > > > > > > >Paul Lam
> > > > > > > > > >   
> > > > > > > > > >2022年6月13日 16:31，Lincoln Lee <
> > > > > > > lincoln.8...@gmail.com
> > > > > > > > >  写道：
> > > > > > > > > >   
> > > > > > > > > >Congratulations, Jingsong!
> > > > > > > > > >   
> > > > > > > > > >Best,
> > > > > > > > > >Lincoln Lee
> > > > > > > > > >   
> > > > > > > > > >   
> > > > > > > > > >Jark Wu  > > > > > > imj...@gmail.com>
> > > > > > > > > 于2022年6月13日周一 

About the Current22 event

[Becket Qin]

Hi my Flink fellas,

The CFP for the Current22 [1] event is about to close.

The Current event is the next generation of KafkaSummit. It expands the
scope to cover **ALL** the technologies for real-time data, not limited to
Kafka. Given Flink is a leading project in this area, the program committee
is actively looking for speakers from the Flink community.

Please don't hesitate to submit a talk [2] if you are interested!

Thanks,

Jiangjie (Becket) Qin

[1] https://2022.currentevent.io/website/39543/
[2] https://sessionize.com/current-2022/

Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee

[Hangxiang Yu]

Congrats, Jingsong!

Best,
Hangxiang

On Thu, Jun 16, 2022 at 9:46 AM Aitozi  wrote:

> Congrats, Jingsong!
>
> Best,
> Aitozi
>
> Zhuoluo Yang  于2022年6月16日周四 09:26写道：
>
> > Many congratulations to teacher Lee!
> >
> > Thanks,
> > Zhuoluo
> >
> >
> > Dian Fu  于2022年6月16日周四 08:54写道：
> >
> > > Congratulations, Jingsong!
> > >
> > > Regards,
> > > Dian
> > >
> > > On Thu, Jun 16, 2022 at 1:08 AM Yu Li  wrote:
> > >
> > > > Congrats, Jingsong!
> > > >
> > > > Best Regards,
> > > > Yu
> > > >
> > > >
> > > > On Wed, 15 Jun 2022 at 15:26, Sergey Nuyanzin 
> > > wrote:
> > > >
> > > > > Congratulations, Jingsong!
> > > > >
> > > > > On Wed, Jun 15, 2022 at 8:45 AM Jingsong Li <
> jingsongl...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Thanks everyone.
> > > > > >
> > > > > > It's great to be with you in the Flink community!
> > > > > >
> > > > > > Best,
> > > > > > Jingsong
> > > > > >
> > > > > > On Wed, Jun 15, 2022 at 2:11 PM Yun Gao
> >  > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > Congratulations, Jingsong!
> > > > > > >
> > > > > > > Best,
> > > > > > > Yun Gao
> > > > > > >
> > > > > > >
> > > > > > >
> > --
> > > > > > > From:Jing Zhang 
> > > > > > > Send Time:2022 Jun. 14 (Tue.) 11:05
> > > > > > > To:dev 
> > > > > > > Subject:Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong
> Lee
> > > > > > >
> > > > > > > Congratulations, Jingsong!
> > > > > > >
> > > > > > > Best,
> > > > > > > Jing Zhang
> > > > > > >
> > > > > > > Leonard Xu  于2022年6月14日周二 10:54写道：
> > > > > > >
> > > > > > > > Congratulations, Jingsong!
> > > > > > > >
> > > > > > > >
> > > > > > > > Best,
> > > > > > > > Leonard
> > > > > > > >
> > > > > > > > > 2022年6月13日 下午6:52，刘首维  写道：
> > > > > > > > >
> > > > > > > > > Congratulations and well deserved, Jingsong!
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Best regards,
> > > > > > > > > Shouwei
> > > > > > > > > --原始邮件--
> > > > > > > > > 发件人:
> > > > > > > > "dev"
> > > > > > > >   <
> > > > > > luoyu...@alumni.sjtu.edu.cn
> > > > > > > > ;
> > > > > > > > > 发送时间:2022年6月13日(星期一) 晚上6:09
> > > > > > > > > 收件人:"dev" > > > dev@flink.apache.org
> > > > > > >;
> > > > > > > > >
> > > > > > > > > 主题:Re: [ANNOUNCE] New Apache Flink PMC Member -
> > Jingsong
> > > > Lee
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Congratulations, Jingsong!
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Best regards,
> > > > > > > > > Yuxia
> > > > > > > > >
> > > > > > > > > - 原始邮件 -
> > > > > > > > > 发件人: "Yun Tang"  > > > > > > > > 收件人: "dev"  > > > > > > > > 发送时间: 星期一, 2022年 6 月 13日 下午 6:12:24
> > > > > > > > > 主题: Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong
> Lee
> > > > > > > > >
> > > > > > > > > Congratulations, Jingsong! Well deserved.
> > > > > > > > >
> > > > > > > > > Best
> > > > > > > > > Yun Tang
> > > > > > > > > 
> > > > > > > > > From: Xingbo Huang  > > > > > > > > Sent: Monday, June 13, 2022 17:39
> > > > > > > > > To: dev  > > > > > > > > Subject: Re: [ANNOUNCE] New Apache Flink PMC Member -
> > Jingsong
> > > > Lee
> > > > > > > > >
> > > > > > > > > Congratulations, Jingsong!
> > > > > > > > >
> > > > > > > > > Best,
> > > > > > > > > Xingbo
> > > > > > > > >
> > > > > > > > > Jane Chan  17:23写道：
> > > > > > > > >
> > > > > > > > >  Congratulations, Jingsong!
> > > > > > > > > 
> > > > > > > > >  Best,
> > > > > > > > >  Jane Chan
> > > > > > > > > 
> > > > > > > > >  On Mon, Jun 13, 2022 at 4:43 PM Shuo Cheng <
> > > > > njucs...@gmail.com
> > > > > > > >  wrote:
> > > > > > > > > 
> > > > > > > > >   Congratulations, Jingsong!
> > > > > > > > >  
> > > > > > > > >   On 6/13/22, Paul Lam  >  > > > > > > > paullin3...@gmail.com> wrote:
> > > > > > > > >Congrats, Jingsong! Well deserved!
> > > > > > > > >   
> > > > > > > > >Best,
> > > > > > > > >Paul Lam
> > > > > > > > >   
> > > > > > > > >2022年6月13日 16:31，Lincoln Lee <
> > > > > > lincoln.8...@gmail.com
> > > > > > > >  写道：
> > > > > > > > >   
> > > > > > > > >Congratulations, Jingsong!
> > > > > > > > >   
> > > > > > > > >Best,
> > > > > > > > >Lincoln Lee
> > > > > > > > >   
> > > > > > > > >   
> > > > > > > > >Jark Wu  > > > > > imj...@gmail.com>
> > > > > > > > 于2022年6月13日周一 16:29写道：
> > > > > > > > >   
> > > > > > > > >Congrats, Jingsong!
> > > > > > > > >   
> > > > > > > > >Cheers,
> > > > > > > > >Jark
> > > > > > > > >   
> > > > > > > > >On Mon, 13 Jun 2022 at 16:16,
> Jiangang
> > > > Liu <
> > > > > > > > >  liujiangangp...@gmail.com  > > liujiangangp...@gmail.com
> > > > > > >
> > > > > > > > >wrote:
> > > > > > > > >   
> > > > > > > > >Congratulations, Jingsong!
> > > > 

Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee

[Aitozi]

Congrats, Jingsong!

Best,
Aitozi

Zhuoluo Yang  于2022年6月16日周四 09:26写道：

> Many congratulations to teacher Lee!
>
> Thanks,
> Zhuoluo
>
>
> Dian Fu  于2022年6月16日周四 08:54写道：
>
> > Congratulations, Jingsong!
> >
> > Regards,
> > Dian
> >
> > On Thu, Jun 16, 2022 at 1:08 AM Yu Li  wrote:
> >
> > > Congrats, Jingsong!
> > >
> > > Best Regards,
> > > Yu
> > >
> > >
> > > On Wed, 15 Jun 2022 at 15:26, Sergey Nuyanzin 
> > wrote:
> > >
> > > > Congratulations, Jingsong!
> > > >
> > > > On Wed, Jun 15, 2022 at 8:45 AM Jingsong Li 
> > > > wrote:
> > > >
> > > > > Thanks everyone.
> > > > >
> > > > > It's great to be with you in the Flink community!
> > > > >
> > > > > Best,
> > > > > Jingsong
> > > > >
> > > > > On Wed, Jun 15, 2022 at 2:11 PM Yun Gao
>  > >
> > > > > wrote:
> > > > > >
> > > > > > Congratulations, Jingsong!
> > > > > >
> > > > > > Best,
> > > > > > Yun Gao
> > > > > >
> > > > > >
> > > > > >
> --
> > > > > > From:Jing Zhang 
> > > > > > Send Time:2022 Jun. 14 (Tue.) 11:05
> > > > > > To:dev 
> > > > > > Subject:Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > > > > >
> > > > > > Congratulations, Jingsong!
> > > > > >
> > > > > > Best,
> > > > > > Jing Zhang
> > > > > >
> > > > > > Leonard Xu  于2022年6月14日周二 10:54写道：
> > > > > >
> > > > > > > Congratulations, Jingsong!
> > > > > > >
> > > > > > >
> > > > > > > Best,
> > > > > > > Leonard
> > > > > > >
> > > > > > > > 2022年6月13日 下午6:52，刘首维  写道：
> > > > > > > >
> > > > > > > > Congratulations and well deserved, Jingsong!
> > > > > > > >
> > > > > > > >
> > > > > > > > Best regards,
> > > > > > > > Shouwei
> > > > > > > > --原始邮件--
> > > > > > > > 发件人:
> > > > > > > "dev"
> > > > > > >   <
> > > > > luoyu...@alumni.sjtu.edu.cn
> > > > > > > ;
> > > > > > > > 发送时间:2022年6月13日(星期一) 晚上6:09
> > > > > > > > 收件人:"dev" > > dev@flink.apache.org
> > > > > >;
> > > > > > > >
> > > > > > > > 主题:Re: [ANNOUNCE] New Apache Flink PMC Member -
> Jingsong
> > > Lee
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Congratulations, Jingsong!
> > > > > > > >
> > > > > > > >
> > > > > > > > Best regards,
> > > > > > > > Yuxia
> > > > > > > >
> > > > > > > > - 原始邮件 -
> > > > > > > > 发件人: "Yun Tang"  > > > > > > > 收件人: "dev"  > > > > > > > 发送时间: 星期一, 2022年 6 月 13日 下午 6:12:24
> > > > > > > > 主题: Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > > > > > > >
> > > > > > > > Congratulations, Jingsong! Well deserved.
> > > > > > > >
> > > > > > > > Best
> > > > > > > > Yun Tang
> > > > > > > > 
> > > > > > > > From: Xingbo Huang  > > > > > > > Sent: Monday, June 13, 2022 17:39
> > > > > > > > To: dev  > > > > > > > Subject: Re: [ANNOUNCE] New Apache Flink PMC Member -
> Jingsong
> > > Lee
> > > > > > > >
> > > > > > > > Congratulations, Jingsong!
> > > > > > > >
> > > > > > > > Best,
> > > > > > > > Xingbo
> > > > > > > >
> > > > > > > > Jane Chan  > > > > > > >
> > > > > > > >  Congratulations, Jingsong!
> > > > > > > > 
> > > > > > > >  Best,
> > > > > > > >  Jane Chan
> > > > > > > > 
> > > > > > > >  On Mon, Jun 13, 2022 at 4:43 PM Shuo Cheng <
> > > > njucs...@gmail.com
> > > > > > >  wrote:
> > > > > > > > 
> > > > > > > >   Congratulations, Jingsong!
> > > > > > > >  
> > > > > > > >   On 6/13/22, Paul Lam   > > > > > > paullin3...@gmail.com> wrote:
> > > > > > > >Congrats, Jingsong! Well deserved!
> > > > > > > >   
> > > > > > > >Best,
> > > > > > > >Paul Lam
> > > > > > > >   
> > > > > > > >2022年6月13日 16:31，Lincoln Lee <
> > > > > lincoln.8...@gmail.com
> > > > > > >  写道：
> > > > > > > >   
> > > > > > > >Congratulations, Jingsong!
> > > > > > > >   
> > > > > > > >Best,
> > > > > > > >Lincoln Lee
> > > > > > > >   
> > > > > > > >   
> > > > > > > >Jark Wu  > > > > imj...@gmail.com>
> > > > > > > 于2022年6月13日周一 16:29写道：
> > > > > > > >   
> > > > > > > >Congrats, Jingsong!
> > > > > > > >   
> > > > > > > >Cheers,
> > > > > > > >Jark
> > > > > > > >   
> > > > > > > >On Mon, 13 Jun 2022 at 16:16, Jiangang
> > > Liu <
> > > > > > > >  liujiangangp...@gmail.com  > liujiangangp...@gmail.com
> > > > > >
> > > > > > > >wrote:
> > > > > > > >   
> > > > > > > >Congratulations, Jingsong!
> > > > > > > >   
> > > > > > > >Best,
> > > > > > > >Jiangang Liu
> > > > > > > >   
> > > > > > > >Martijn Visser <
> > > > martijnvis...@apache.org
> > > > > > >  于2022年6月13日周一 16:06写道：
> > > > > > > >   
> > > > > > > >Like everyone has mentioned,
> > this
> > > is
> > > > > very
> > > > > > > well deserved.
> > > > > > > >Congratulations!
> > > > > > > >   
> > > > > > > >Op ma 13 jun. 2022 om 09:57
> > > schreef
> > 

Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee

[Zhuoluo Yang]

Many congratulations to teacher Lee!

Thanks,
Zhuoluo


Dian Fu  于2022年6月16日周四 08:54写道：

> Congratulations, Jingsong!
>
> Regards,
> Dian
>
> On Thu, Jun 16, 2022 at 1:08 AM Yu Li  wrote:
>
> > Congrats, Jingsong!
> >
> > Best Regards,
> > Yu
> >
> >
> > On Wed, 15 Jun 2022 at 15:26, Sergey Nuyanzin 
> wrote:
> >
> > > Congratulations, Jingsong!
> > >
> > > On Wed, Jun 15, 2022 at 8:45 AM Jingsong Li 
> > > wrote:
> > >
> > > > Thanks everyone.
> > > >
> > > > It's great to be with you in the Flink community!
> > > >
> > > > Best,
> > > > Jingsong
> > > >
> > > > On Wed, Jun 15, 2022 at 2:11 PM Yun Gao  >
> > > > wrote:
> > > > >
> > > > > Congratulations, Jingsong!
> > > > >
> > > > > Best,
> > > > > Yun Gao
> > > > >
> > > > >
> > > > > --
> > > > > From:Jing Zhang 
> > > > > Send Time:2022 Jun. 14 (Tue.) 11:05
> > > > > To:dev 
> > > > > Subject:Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > > > >
> > > > > Congratulations, Jingsong!
> > > > >
> > > > > Best,
> > > > > Jing Zhang
> > > > >
> > > > > Leonard Xu  于2022年6月14日周二 10:54写道：
> > > > >
> > > > > > Congratulations, Jingsong!
> > > > > >
> > > > > >
> > > > > > Best,
> > > > > > Leonard
> > > > > >
> > > > > > > 2022年6月13日 下午6:52，刘首维  写道：
> > > > > > >
> > > > > > > Congratulations and well deserved, Jingsong!
> > > > > > >
> > > > > > >
> > > > > > > Best regards,
> > > > > > > Shouwei
> > > > > > > --原始邮件--
> > > > > > > 发件人:
> > > > > > "dev"
> > > > > >   <
> > > > luoyu...@alumni.sjtu.edu.cn
> > > > > > ;
> > > > > > > 发送时间:2022年6月13日(星期一) 晚上6:09
> > > > > > > 收件人:"dev" > dev@flink.apache.org
> > > > >;
> > > > > > >
> > > > > > > 主题:Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong
> > Lee
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Congratulations, Jingsong!
> > > > > > >
> > > > > > >
> > > > > > > Best regards,
> > > > > > > Yuxia
> > > > > > >
> > > > > > > - 原始邮件 -
> > > > > > > 发件人: "Yun Tang"  > > > > > > 收件人: "dev"  > > > > > > 发送时间: 星期一, 2022年 6 月 13日 下午 6:12:24
> > > > > > > 主题: Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > > > > > >
> > > > > > > Congratulations, Jingsong! Well deserved.
> > > > > > >
> > > > > > > Best
> > > > > > > Yun Tang
> > > > > > > 
> > > > > > > From: Xingbo Huang  > > > > > > Sent: Monday, June 13, 2022 17:39
> > > > > > > To: dev  > > > > > > Subject: Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong
> > Lee
> > > > > > >
> > > > > > > Congratulations, Jingsong!
> > > > > > >
> > > > > > > Best,
> > > > > > > Xingbo
> > > > > > >
> > > > > > > Jane Chan  > > > > > >
> > > > > > >  Congratulations, Jingsong!
> > > > > > > 
> > > > > > >  Best,
> > > > > > >  Jane Chan
> > > > > > > 
> > > > > > >  On Mon, Jun 13, 2022 at 4:43 PM Shuo Cheng <
> > > njucs...@gmail.com
> > > > > >  wrote:
> > > > > > > 
> > > > > > >   Congratulations, Jingsong!
> > > > > > >  
> > > > > > >   On 6/13/22, Paul Lam  > > > > > paullin3...@gmail.com> wrote:
> > > > > > >Congrats, Jingsong! Well deserved!
> > > > > > >   
> > > > > > >Best,
> > > > > > >Paul Lam
> > > > > > >   
> > > > > > >2022年6月13日 16:31，Lincoln Lee <
> > > > lincoln.8...@gmail.com
> > > > > >  写道：
> > > > > > >   
> > > > > > >Congratulations, Jingsong!
> > > > > > >   
> > > > > > >Best,
> > > > > > >Lincoln Lee
> > > > > > >   
> > > > > > >   
> > > > > > >Jark Wu  > > > imj...@gmail.com>
> > > > > > 于2022年6月13日周一 16:29写道：
> > > > > > >   
> > > > > > >Congrats, Jingsong!
> > > > > > >   
> > > > > > >Cheers,
> > > > > > >Jark
> > > > > > >   
> > > > > > >On Mon, 13 Jun 2022 at 16:16, Jiangang
> > Liu <
> > > > > > >  liujiangangp...@gmail.com  liujiangangp...@gmail.com
> > > > >
> > > > > > >wrote:
> > > > > > >   
> > > > > > >Congratulations, Jingsong!
> > > > > > >   
> > > > > > >Best,
> > > > > > >Jiangang Liu
> > > > > > >   
> > > > > > >Martijn Visser <
> > > martijnvis...@apache.org
> > > > > >  于2022年6月13日周一 16:06写道：
> > > > > > >   
> > > > > > >Like everyone has mentioned,
> this
> > is
> > > > very
> > > > > > well deserved.
> > > > > > >Congratulations!
> > > > > > >   
> > > > > > >Op ma 13 jun. 2022 om 09:57
> > schreef
> > > > > > Benchao Li <
> > > > > > >  libenc...@apache.org 
> > > > > > >   :
> > > > > > >   
> > > > > > >Congratulations,
> > Jingsong!
> > > > Well
> > > > > > deserved.
> > > > > > >   
> > > > > > >Rui Fan <
> 1996fan...@gmail.com
> > > > > >  于2022年6月13日周一 15:53写道：
> > > > > > >   
> > > > > > >Congratulations,
> Jingsong!
> > > > > > >   
> > > > > > >

Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee

[Shengkai Fang]

Congratulations, Jingsong!

Best,
Shengkai

Dian Fu  于2022年6月16日周四 08:54写道：

> Congratulations, Jingsong!
>
> Regards,
> Dian
>
> On Thu, Jun 16, 2022 at 1:08 AM Yu Li  wrote:
>
> > Congrats, Jingsong!
> >
> > Best Regards,
> > Yu
> >
> >
> > On Wed, 15 Jun 2022 at 15:26, Sergey Nuyanzin 
> wrote:
> >
> > > Congratulations, Jingsong!
> > >
> > > On Wed, Jun 15, 2022 at 8:45 AM Jingsong Li 
> > > wrote:
> > >
> > > > Thanks everyone.
> > > >
> > > > It's great to be with you in the Flink community!
> > > >
> > > > Best,
> > > > Jingsong
> > > >
> > > > On Wed, Jun 15, 2022 at 2:11 PM Yun Gao  >
> > > > wrote:
> > > > >
> > > > > Congratulations, Jingsong!
> > > > >
> > > > > Best,
> > > > > Yun Gao
> > > > >
> > > > >
> > > > > --
> > > > > From:Jing Zhang 
> > > > > Send Time:2022 Jun. 14 (Tue.) 11:05
> > > > > To:dev 
> > > > > Subject:Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > > > >
> > > > > Congratulations, Jingsong!
> > > > >
> > > > > Best,
> > > > > Jing Zhang
> > > > >
> > > > > Leonard Xu  于2022年6月14日周二 10:54写道：
> > > > >
> > > > > > Congratulations, Jingsong!
> > > > > >
> > > > > >
> > > > > > Best,
> > > > > > Leonard
> > > > > >
> > > > > > > 2022年6月13日 下午6:52，刘首维  写道：
> > > > > > >
> > > > > > > Congratulations and well deserved, Jingsong!
> > > > > > >
> > > > > > >
> > > > > > > Best regards,
> > > > > > > Shouwei
> > > > > > > --原始邮件--
> > > > > > > 发件人:
> > > > > > "dev"
> > > > > >   <
> > > > luoyu...@alumni.sjtu.edu.cn
> > > > > > ;
> > > > > > > 发送时间:2022年6月13日(星期一) 晚上6:09
> > > > > > > 收件人:"dev" > dev@flink.apache.org
> > > > >;
> > > > > > >
> > > > > > > 主题:Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong
> > Lee
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Congratulations, Jingsong!
> > > > > > >
> > > > > > >
> > > > > > > Best regards,
> > > > > > > Yuxia
> > > > > > >
> > > > > > > - 原始邮件 -
> > > > > > > 发件人: "Yun Tang"  > > > > > > 收件人: "dev"  > > > > > > 发送时间: 星期一, 2022年 6 月 13日 下午 6:12:24
> > > > > > > 主题: Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > > > > > >
> > > > > > > Congratulations, Jingsong! Well deserved.
> > > > > > >
> > > > > > > Best
> > > > > > > Yun Tang
> > > > > > > 
> > > > > > > From: Xingbo Huang  > > > > > > Sent: Monday, June 13, 2022 17:39
> > > > > > > To: dev  > > > > > > Subject: Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong
> > Lee
> > > > > > >
> > > > > > > Congratulations, Jingsong!
> > > > > > >
> > > > > > > Best,
> > > > > > > Xingbo
> > > > > > >
> > > > > > > Jane Chan  > > > > > >
> > > > > > >  Congratulations, Jingsong!
> > > > > > > 
> > > > > > >  Best,
> > > > > > >  Jane Chan
> > > > > > > 
> > > > > > >  On Mon, Jun 13, 2022 at 4:43 PM Shuo Cheng <
> > > njucs...@gmail.com
> > > > > >  wrote:
> > > > > > > 
> > > > > > >   Congratulations, Jingsong!
> > > > > > >  
> > > > > > >   On 6/13/22, Paul Lam  > > > > > paullin3...@gmail.com> wrote:
> > > > > > >Congrats, Jingsong! Well deserved!
> > > > > > >   
> > > > > > >Best,
> > > > > > >Paul Lam
> > > > > > >   
> > > > > > >2022年6月13日 16:31，Lincoln Lee <
> > > > lincoln.8...@gmail.com
> > > > > >  写道：
> > > > > > >   
> > > > > > >Congratulations, Jingsong!
> > > > > > >   
> > > > > > >Best,
> > > > > > >Lincoln Lee
> > > > > > >   
> > > > > > >   
> > > > > > >Jark Wu  > > > imj...@gmail.com>
> > > > > > 于2022年6月13日周一 16:29写道：
> > > > > > >   
> > > > > > >Congrats, Jingsong!
> > > > > > >   
> > > > > > >Cheers,
> > > > > > >Jark
> > > > > > >   
> > > > > > >On Mon, 13 Jun 2022 at 16:16, Jiangang
> > Liu <
> > > > > > >  liujiangangp...@gmail.com  liujiangangp...@gmail.com
> > > > >
> > > > > > >wrote:
> > > > > > >   
> > > > > > >Congratulations, Jingsong!
> > > > > > >   
> > > > > > >Best,
> > > > > > >Jiangang Liu
> > > > > > >   
> > > > > > >Martijn Visser <
> > > martijnvis...@apache.org
> > > > > >  于2022年6月13日周一 16:06写道：
> > > > > > >   
> > > > > > >Like everyone has mentioned,
> this
> > is
> > > > very
> > > > > > well deserved.
> > > > > > >Congratulations!
> > > > > > >   
> > > > > > >Op ma 13 jun. 2022 om 09:57
> > schreef
> > > > > > Benchao Li <
> > > > > > >  libenc...@apache.org 
> > > > > > >   :
> > > > > > >   
> > > > > > >Congratulations,
> > Jingsong!
> > > > Well
> > > > > > deserved.
> > > > > > >   
> > > > > > >Rui Fan <
> 1996fan...@gmail.com
> > > > > >  于2022年6月13日周一 15:53写道：
> > > > > > >   
> > > > > > >Congratulations,
> Jingsong!
> > > > > > >   
> > > > > > >Best,
> > > > > 

Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee

[Dian Fu]

Congratulations, Jingsong!

Regards,
Dian

On Thu, Jun 16, 2022 at 1:08 AM Yu Li  wrote:

> Congrats, Jingsong!
>
> Best Regards,
> Yu
>
>
> On Wed, 15 Jun 2022 at 15:26, Sergey Nuyanzin  wrote:
>
> > Congratulations, Jingsong!
> >
> > On Wed, Jun 15, 2022 at 8:45 AM Jingsong Li 
> > wrote:
> >
> > > Thanks everyone.
> > >
> > > It's great to be with you in the Flink community!
> > >
> > > Best,
> > > Jingsong
> > >
> > > On Wed, Jun 15, 2022 at 2:11 PM Yun Gao 
> > > wrote:
> > > >
> > > > Congratulations, Jingsong!
> > > >
> > > > Best,
> > > > Yun Gao
> > > >
> > > >
> > > > --
> > > > From:Jing Zhang 
> > > > Send Time:2022 Jun. 14 (Tue.) 11:05
> > > > To:dev 
> > > > Subject:Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > > >
> > > > Congratulations, Jingsong!
> > > >
> > > > Best,
> > > > Jing Zhang
> > > >
> > > > Leonard Xu  于2022年6月14日周二 10:54写道：
> > > >
> > > > > Congratulations, Jingsong!
> > > > >
> > > > >
> > > > > Best,
> > > > > Leonard
> > > > >
> > > > > > 2022年6月13日 下午6:52，刘首维  写道：
> > > > > >
> > > > > > Congratulations and well deserved, Jingsong!
> > > > > >
> > > > > >
> > > > > > Best regards,
> > > > > > Shouwei
> > > > > > --原始邮件--
> > > > > > 发件人:
> > > > > "dev"
> > > > >   <
> > > luoyu...@alumni.sjtu.edu.cn
> > > > > ;
> > > > > > 发送时间:2022年6月13日(星期一) 晚上6:09
> > > > > > 收件人:"dev" dev@flink.apache.org
> > > >;
> > > > > >
> > > > > > 主题:Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong
> Lee
> > > > > >
> > > > > >
> > > > > >
> > > > > > Congratulations, Jingsong!
> > > > > >
> > > > > >
> > > > > > Best regards,
> > > > > > Yuxia
> > > > > >
> > > > > > - 原始邮件 -
> > > > > > 发件人: "Yun Tang"  > > > > > 收件人: "dev"  > > > > > 发送时间: 星期一, 2022年 6 月 13日 下午 6:12:24
> > > > > > 主题: Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > > > > >
> > > > > > Congratulations, Jingsong! Well deserved.
> > > > > >
> > > > > > Best
> > > > > > Yun Tang
> > > > > > 
> > > > > > From: Xingbo Huang  > > > > > Sent: Monday, June 13, 2022 17:39
> > > > > > To: dev  > > > > > Subject: Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong
> Lee
> > > > > >
> > > > > > Congratulations, Jingsong!
> > > > > >
> > > > > > Best,
> > > > > > Xingbo
> > > > > >
> > > > > > Jane Chan  > > > > >
> > > > > >  Congratulations, Jingsong!
> > > > > > 
> > > > > >  Best,
> > > > > >  Jane Chan
> > > > > > 
> > > > > >  On Mon, Jun 13, 2022 at 4:43 PM Shuo Cheng <
> > njucs...@gmail.com
> > > > >  wrote:
> > > > > > 
> > > > > >   Congratulations, Jingsong!
> > > > > >  
> > > > > >   On 6/13/22, Paul Lam  > > > > paullin3...@gmail.com> wrote:
> > > > > >Congrats, Jingsong! Well deserved!
> > > > > >   
> > > > > >Best,
> > > > > >Paul Lam
> > > > > >   
> > > > > >2022年6月13日 16:31，Lincoln Lee <
> > > lincoln.8...@gmail.com
> > > > >  写道：
> > > > > >   
> > > > > >Congratulations, Jingsong!
> > > > > >   
> > > > > >Best,
> > > > > >Lincoln Lee
> > > > > >   
> > > > > >   
> > > > > >Jark Wu  > > imj...@gmail.com>
> > > > > 于2022年6月13日周一 16:29写道：
> > > > > >   
> > > > > >Congrats, Jingsong!
> > > > > >   
> > > > > >Cheers,
> > > > > >Jark
> > > > > >   
> > > > > >On Mon, 13 Jun 2022 at 16:16, Jiangang
> Liu <
> > > > > >  liujiangangp...@gmail.com  > > >
> > > > > >wrote:
> > > > > >   
> > > > > >Congratulations, Jingsong!
> > > > > >   
> > > > > >Best,
> > > > > >Jiangang Liu
> > > > > >   
> > > > > >Martijn Visser <
> > martijnvis...@apache.org
> > > > >  于2022年6月13日周一 16:06写道：
> > > > > >   
> > > > > >Like everyone has mentioned, this
> is
> > > very
> > > > > well deserved.
> > > > > >Congratulations!
> > > > > >   
> > > > > >Op ma 13 jun. 2022 om 09:57
> schreef
> > > > > Benchao Li <
> > > > > >  libenc...@apache.org 
> > > > > >   :
> > > > > >   
> > > > > >Congratulations,
> Jingsong!
> > > Well
> > > > > deserved.
> > > > > >   
> > > > > >Rui Fan <1996fan...@gmail.com
> > > > >  于2022年6月13日周一 15:53写道：
> > > > > >   
> > > > > >Congratulations, Jingsong!
> > > > > >   
> > > > > >Best,
> > > > > >Rui Fan
> > > > > >   
> > > > > >On Mon, Jun 13, 2022 at
> 3:40
> > > PM
> > > > > LuNing Wang <
> > > > > >  wang4lun...@gmail.com 
> > > > > >   
> > > > > >wrote:
> > > > > >   
> > > > > >Congratulations,
> > Jingsong!
> > > > > >   
> > > > > >Best,
> > > > > >LuNing Wang
> > > > > >   
> > > > > >Ingo Bürk <
> > > > > airbla...@apache.org 
> 

[jira] [Created] (FLINK-28085) Close all the pending Pulsar transactions when flink shutdown the pipeline.

[Yufan Sheng (Jira)]

Yufan Sheng created FLINK-28085:
---

 Summary: Close all the pending Pulsar transactions when flink 
shutdown the pipeline.
 Key: FLINK-28085
 URL: https://issues.apache.org/jira/browse/FLINK-28085
 Project: Flink
  Issue Type: Bug
  Components: Connectors / Pulsar
Affects Versions: 1.14.4, 1.15.0
Reporter: Yufan Sheng
 Fix For: 1.16.0


Currently transactionId is not persisted. After a job restart we lose handle to 
the transaction which is still not aborted in Pulsar broker. Pulsar broker will 
abort these hanging transactions after a timeout but this is not desirable. We 
need to close all the pending transactionId.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Created] (FLINK-28084) Pulsar unordered reader should disable retry and delete reconsume logic.

[Yufan Sheng (Jira)]

Yufan Sheng created FLINK-28084:
---

 Summary: Pulsar unordered reader should disable retry and delete 
reconsume logic.
 Key: FLINK-28084
 URL: https://issues.apache.org/jira/browse/FLINK-28084
 Project: Flink
  Issue Type: Bug
  Components: Connectors / Pulsar
Affects Versions: 1.14.4, 1.15.0
Reporter: Yufan Sheng
 Fix For: 1.16.0


Pulsar unordered reader is used for Shared and Key_Shared subscriptions. It 
would reconsume a message if it didn't acknowledge in a transaction. But this 
didn't works now. Because we don't use Pulsar's Multiple consumer. The best way 
to solve this problem is just delete this reconsumeLater logic.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Re: Re: [DISCUSS] FLIP-240: Introduce "ANALYZE TABLE" Syntax

[Jing Ge]

Hi Godfrey,

Thanks for driving this! There are some areas where I couldn't find enough
information in the FLIP, just wondering if I could get more
explanation from you w.r.t. the following questions:

1. When will the converted SELECT statement of the ANALYZE TABLE be
submitted? right after the CREATE TABLE?

2. Will it be submitted periodically to keep the statistical data
up-to-date, since the data might be mutable?

3. " If no partition is specified, the statistics will be gathered for all
partitions"  - I think this is fine for multi-level partitions, e.g. PARTITION
(ds='2022-06-01') means two partitions: PARTITION (ds='2022-06-01', hr=1)
and PARTITION (ds='2022-06-01', hr=2), because it will save a lot of code
and therefore help developer work more efficiently. If we use this rule for
top level partitions, It might not be strong enough to avoid human
error, e.g. developer might trigger huge selection on the table with many
partitions, when he forgot to write the partition in the ANALYZE TABLE
script. In this case, I would suggest using FOR ALL PARTITIONS explicitly
just like FOR ALL COLUMNS.

Best regards,
Jing


On Wed, Jun 15, 2022 at 10:16 AM godfrey he  wrote:

> Hi Jark,
>
> Thanks for the inputs.
>
> >Do we need to provide DESC EXTENDED  statement like Spark[1]
> to
> >show statistic for table/partition/columns?
> We do have supported `DESC EXTENDED` syntax, but currently only table
> schema
> will be display, I think we just need a JIRA to support it.
>
> > is it possible to ignore execution mode and force using batch mode for
> the statement?
> As I replied above, The semantics of `ANALYZE TABLE` does not
> distinguish batch and streaming,
> It works for both batch and streaming, but the result of unbounded
> sources is meaningless.
> Currently, I throw exception for streaming mode,
> and we can support streaming mode with bounded source in the future.
>
> Best,
> Godfrey
>
> Jark Wu  于2022年6月14日周二 17:56写道：
> >
> > Hi Godfrey, thanks for starting this discussion, this is a great feature
> > for batch users.
> >
> > The FLIP looks good to me in general.
> >
> > I only have 2 comments:
> >
> > 1) How do users know whether the given table or partition contains
> required
> > statistics?
> > Do we need to provide DESC EXTENDED  statement like Spark[1]
> to
> > show statistic for table/partition/columns?
> >
> > 2) If ANALYZE TABLE can only run in batch mode, is it possible to ignore
> > execution mode
> > and force using batch mode for the statement? From my perspective,
> ANALYZE
> > TABLE
> > is an auxiliary statement similar to SHOW TABLES but heavier, which
> doesn't
> > care about
> > environment execution mode.
> >
> > Best,
> > Jark
> >
> > [1]:
> >
> https://spark.apache.org/docs/3.0.0-preview/sql-ref-syntax-aux-analyze-table.html
> >
> > On Tue, 14 Jun 2022 at 13:52, Jing Ge  wrote:
> >
> > > Hi 华宗
> > >
> > > 退订请发送任意消息至dev-unsubscr...@flink.apache.org
> > > In order to unsubscribe, please send an email to
> > > dev-unsubscr...@flink.apache.org
> > >
> > > Thanks
> > >
> > > Best regards,
> > > Jing
> > >
> > >
> > > On Tue, Jun 14, 2022 at 2:05 AM 华宗  wrote:
> > >
> > > > 退订
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > At 2022-06-13 22:44:24, "cao zou"  wrote:
> > > > >Hi godfrey, thanks for your detail explanation.
> > > > >After explaining and glancing over the FLIP-231, I think it is
> > > > >really need, +1 for this and looking forward to it.
> > > > >
> > > > >best
> > > > >zoucao
> > > > >
> > > > >godfrey he  于2022年6月13日周一 14:43写道：
> > > > >
> > > > >> Hi Ingo,
> > > > >>
> > > > >> The semantics does not distinguish batch and streaming,
> > > > >> It works for both batch and streaming, but the result of
> > > > >> unbounded sources is meaningless.
> > > > >> Currently, I throw exception for streaming mode,
> > > > >> and we can support streaming mode with bounded source
> > > > >> in the future.
> > > > >>
> > > > >> Best,
> > > > >> Godfrey
> > > > >>
> > > > >> Ingo Bürk  于2022年6月13日周一 14:17写道：
> > > > >> >
> > > > >> > Hi Godfrey,
> > > > >> >
> > > > >> > thank you for the explanation. A SELECT is definitely more
> generic
> > > and
> > > > >> > will work for all connectors automatically. As such I think
> it's a
> > > > good
> > > > >> > baseline solution regardless.
> > > > >> >
> > > > >> > We can also think about allowing connector-specific
> optimizations in
> > > > the
> > > > >> > future, but I do like your idea of letting the optimizer rules
> > > > perform a
> > > > >> > lot of the work here already by leveraging existing
> optimizations.
> > > > >> > Similarly things like non-null counts of non-nullable columns
> would
> > > > (or
> > > > >> > at least could) be handled by the optimizer rules already.
> > > > >> >
> > > > >> > So as far as that point goes, +1 to the generic approach.
> > > > >> >
> > > > >> > One more point, though: In general we should avoid 

Re: [DISCUSS] Deprecate SourceFunction APIs

[Alexander Fedulov]

Thank you all for your valuable input and participation in the discussion

The vote is open now [1]

[1] https://lists.apache.org/thread/kv9rj3w2rmkb8jtss5bqffhw57or7v8v

Best,
Alexander Fedulov




On Tue, Jun 14, 2022 at 10:21 PM Jing Ge  wrote:

> Hi Martijn,
>
> Yes, that is exactly what I tried to say implicitly in a polite manner. :))
>
> Best regards,
> Jing
>
>
> On Tue, Jun 14, 2022 at 8:12 PM Martijn Visser 
> wrote:
>
> > Hi Alex and Jing,
> >
> > According to the Flink Bylaws and FLIP guide, this change would be a
> > "change that impacts the public interfaces of the project". I do see
> little
> > value in creating a special deprecation FLIP, but I do think it requires
> a
> > [VOTE] thread which follows the FLIP approval process. So basically I
> would
> > create a VOTE thread while linking to this discussion thread for context.
> >
> > Best regards,
> >
> > Martijn
> >
> > [1] https://cwiki.apache.org/confluence/display/FLINK/Flink+Bylaws
> > [2]
> >
> >
> https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals#FlinkImprovementProposals-Whatisconsidereda%22majorchange%22thatneedsaFLIP
> > ?
> >
> > Op di 14 jun. 2022 om 17:22 schreef Alexander Fedulov <
> > alexan...@ververica.com>:
> >
> > > Hi Jing,
> > >
> > > I don't think we do pure deprecation FLIPs. I am also OK if we consider
> > > consensus in this thread enough to proceed with opening the actual
> > > deprecation PRs for the first two items of the umbrella ticket. In that
> > > case, we can skip the vote.
> > >
> > > What do people prefer? Do you think we need to do a formal vote for
> > > this change or should we simply kick it off with the first deprecations
> > > based on the discussion above?
> > >
> > > Best,
> > > Alexander Fedulov
> > >
> > > On Tue, Jun 14, 2022 at 4:26 PM Jing Ge  wrote:
> > >
> > > > Hi Alex,
> > > >
> > > > I guess you are meaning to start a new voting thread following the
> FLIP
> > > > discussion concept. Looking forward to it!
> > > >
> > > > Best regards,
> > > > Jing
> > > >
> > > > On Tue, Jun 14, 2022 at 3:35 PM Alexander Fedulov <
> > > alexan...@ververica.com
> > > > >
> > > > wrote:
> > > >
> > > > > Hi Becket,
> > > > >
> > > > > thanks for your feedback. As proposed, I started an umbrella ticket
> > [1]
> > > > to
> > > > > collect all the
> > > > > steps needed. Please add any missing items.
> > > > >
> > > > > Judging by the discussion on this thread I propose to open a vote
> on
> > > the
> > > > > first two
> > > > > subtasks since they are immediately actionable [2] [3].
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/FLINK-28045
> > > > > [2] https://issues.apache.org/jira/browse/FLINK-28046
> > > > > [3] https://issues.apache.org/jira/browse/FLINK-28047
> > > > >
> > > > > Best,
> > > > > Alexander Fedulov
> > > > >
> > > > >
> > > > > On Tue, Jun 14, 2022 at 4:37 AM Becket Qin 
> > > wrote:
> > > > >
> > > > > > In general, I'll give a big +1 to deprecating the SourceFunction.
> > > > > >
> > > > > > That said, it is indeed worth looking into what might be missing
> or
> > > > less
> > > > > > easy to implement with FLIP-27 Source compared with the
> > > SourceFunction.
> > > > > > Maybe we can just compile a list of things to do in order to
> fully
> > > > > > deprecate the SourceFunction. As far as I am aware of, there are
> > two
> > > > > things
> > > > > > that need to be taken care of：
> > > > > >
> > > > > > 1. A simple high level API, as Jing mentioned, that makes simple
> > > cases
> > > > > that
> > > > > > do not involve the split enumerator easier. Ideally this should
> be
> > as
> > > > > > simple as SourceFunction, if not simpler. Off the top of my
> head, I
> > > > > think a
> > > > > > default no-op split enumerator will just do the work. And the
> data
> > > > > > generator of FLIP-238 could be an implementation using this high
> > > level
> > > > > API.
> > > > > >
> > > > > > 2. FLIP-208, which allows users to stop the job upon receiving a
> > > record
> > > > > in
> > > > > > the stream.
> > > > > >
> > > > > > Is there anything else that we have heard from the users /
> > connector
> > > > > > developers that needs some attention?
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Jiangjie (Becket) Qin
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Fri, Jun 10, 2022 at 3:25 PM David Anderson <
> > dander...@apache.org
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > +1 for deprecating SourceFunction from me as well. And a big
> > THANK
> > > > YOU
> > > > > to
> > > > > > > Alex Fedulov for bringing forward FLIP-238.
> > > > > > >
> > > > > > > David
> > > > > > >
> > > > > > > On Fri, Jun 10, 2022 at 4:03 AM Lijie Wang <
> > > wangdachui9...@gmail.com
> > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > Sorry for my mistake. The
> > `StreamExecutionEnvironment#readFiles`
> > > > and
> > > > > > can
> > > > > > > be
> > > > > > > > easily replaced by
> > > > > > 

[jira] [Created] (FLINK-28083) PulsarSource cannot work with object-reusing DeserializationSchema.

[Yufan Sheng (Jira)]

Yufan Sheng created FLINK-28083:
---

 Summary: PulsarSource cannot work with object-reusing 
DeserializationSchema.
 Key: FLINK-28083
 URL: https://issues.apache.org/jira/browse/FLINK-28083
 Project: Flink
  Issue Type: Bug
  Components: Connectors / Pulsar
Affects Versions: 1.14.4, 1.15.0
Reporter: Yufan Sheng
 Fix For: 1.16.0


This issue is the same as Kafka's 
https://issues.apache.org/jira/browse/FLINK-25132



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[VOTE] Deprecate SourceFunction API

[Alexander Fedulov]

Hi everyone,

following the discussion in [1], I would like to open up a vote for
deprecating the SourceFunction API.

An overview of the steps required for being able to drop this
API in the next major version is maintained in the umbrella
FLINK-28045 ticket [2].

This proposition implies marking the SourceFunction interface
itself as @Deprecated  + redirecting to the FLIP-27 Source API
right away, without waiting for all the subtasks to be completed.

[1] https://lists.apache.org/thread/d6cwqw9b3105wcpdkwq7rr4s7x4ywqr9
[2] https://issues.apache.org/jira/browse/FLINK-28045

Best,
Alexander Fedulov

[jira] [Created] (FLINK-28082) Support end to end encryption on Pulsar connector.

[Yufan Sheng (Jira)]

Yufan Sheng created FLINK-28082:
---

 Summary: Support end to end encryption on Pulsar connector.
 Key: FLINK-28082
 URL: https://issues.apache.org/jira/browse/FLINK-28082
 Project: Flink
  Issue Type: Bug
  Components: Connectors / Pulsar
Affects Versions: 1.16.0
Reporter: Yufan Sheng
 Fix For: 1.16.0


Add this Pulsar encryption support:

https://pulsar.apache.org/docs/security-encryption/



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee

[Yu Li]

Congrats, Jingsong!

Best Regards,
Yu


On Wed, 15 Jun 2022 at 15:26, Sergey Nuyanzin  wrote:

> Congratulations, Jingsong!
>
> On Wed, Jun 15, 2022 at 8:45 AM Jingsong Li 
> wrote:
>
> > Thanks everyone.
> >
> > It's great to be with you in the Flink community!
> >
> > Best,
> > Jingsong
> >
> > On Wed, Jun 15, 2022 at 2:11 PM Yun Gao 
> > wrote:
> > >
> > > Congratulations, Jingsong!
> > >
> > > Best,
> > > Yun Gao
> > >
> > >
> > > --
> > > From:Jing Zhang 
> > > Send Time:2022 Jun. 14 (Tue.) 11:05
> > > To:dev 
> > > Subject:Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > >
> > > Congratulations, Jingsong!
> > >
> > > Best,
> > > Jing Zhang
> > >
> > > Leonard Xu  于2022年6月14日周二 10:54写道：
> > >
> > > > Congratulations, Jingsong!
> > > >
> > > >
> > > > Best,
> > > > Leonard
> > > >
> > > > > 2022年6月13日 下午6:52，刘首维  写道：
> > > > >
> > > > > Congratulations and well deserved, Jingsong!
> > > > >
> > > > >
> > > > > Best regards,
> > > > > Shouwei
> > > > > --原始邮件--
> > > > > 发件人:
> > > > "dev"
> > > >   <
> > luoyu...@alumni.sjtu.edu.cn
> > > > ;
> > > > > 发送时间:2022年6月13日(星期一) 晚上6:09
> > > > > 收件人:"dev"mailto:dev@flink.apache.org
> > >;
> > > > >
> > > > > 主题:Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > > > >
> > > > >
> > > > >
> > > > > Congratulations, Jingsong!
> > > > >
> > > > >
> > > > > Best regards,
> > > > > Yuxia
> > > > >
> > > > > - 原始邮件 -
> > > > > 发件人: "Yun Tang"  > > > > 收件人: "dev"  > > > > 发送时间: 星期一, 2022年 6 月 13日 下午 6:12:24
> > > > > 主题: Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > > > >
> > > > > Congratulations, Jingsong! Well deserved.
> > > > >
> > > > > Best
> > > > > Yun Tang
> > > > > 
> > > > > From: Xingbo Huang  > > > > Sent: Monday, June 13, 2022 17:39
> > > > > To: dev  > > > > Subject: Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > > > >
> > > > > Congratulations, Jingsong!
> > > > >
> > > > > Best,
> > > > > Xingbo
> > > > >
> > > > > Jane Chan  > > > >
> > > > >  Congratulations, Jingsong!
> > > > > 
> > > > >  Best,
> > > > >  Jane Chan
> > > > > 
> > > > >  On Mon, Jun 13, 2022 at 4:43 PM Shuo Cheng <
> njucs...@gmail.com
> > > >  wrote:
> > > > > 
> > > > >   Congratulations, Jingsong!
> > > > >  
> > > > >   On 6/13/22, Paul Lam  > > > paullin3...@gmail.com> wrote:
> > > > >Congrats, Jingsong! Well deserved!
> > > > >   
> > > > >Best,
> > > > >Paul Lam
> > > > >   
> > > > >2022年6月13日 16:31，Lincoln Lee <
> > lincoln.8...@gmail.com
> > > >  写道：
> > > > >   
> > > > >Congratulations, Jingsong!
> > > > >   
> > > > >Best,
> > > > >Lincoln Lee
> > > > >   
> > > > >   
> > > > >Jark Wu  > imj...@gmail.com>
> > > > 于2022年6月13日周一 16:29写道：
> > > > >   
> > > > >Congrats, Jingsong!
> > > > >   
> > > > >Cheers,
> > > > >Jark
> > > > >   
> > > > >On Mon, 13 Jun 2022 at 16:16, Jiangang Liu <
> > > > >  liujiangangp...@gmail.com  > >
> > > > >wrote:
> > > > >   
> > > > >Congratulations, Jingsong!
> > > > >   
> > > > >Best,
> > > > >Jiangang Liu
> > > > >   
> > > > >Martijn Visser <
> martijnvis...@apache.org
> > > >  于2022年6月13日周一 16:06写道：
> > > > >   
> > > > >Like everyone has mentioned, this is
> > very
> > > > well deserved.
> > > > >Congratulations!
> > > > >   
> > > > >Op ma 13 jun. 2022 om 09:57 schreef
> > > > Benchao Li <
> > > > >  libenc...@apache.org 
> > > > >   :
> > > > >   
> > > > >Congratulations, Jingsong!
> > Well
> > > > deserved.
> > > > >   
> > > > >Rui Fan <1996fan...@gmail.com
> > > >  于2022年6月13日周一 15:53写道：
> > > > >   
> > > > >Congratulations, Jingsong!
> > > > >   
> > > > >Best,
> > > > >Rui Fan
> > > > >   
> > > > >On Mon, Jun 13, 2022 at 3:40
> > PM
> > > > LuNing Wang <
> > > > >  wang4lun...@gmail.com 
> > > > >   
> > > > >wrote:
> > > > >   
> > > > >Congratulations,
> Jingsong!
> > > > >   
> > > > >Best,
> > > > >LuNing Wang
> > > > >   
> > > > >Ingo Bürk <
> > > > airbla...@apache.org  于2022年6月13日周一
> > > > 15:36写道：
> > > > >   
> > > > >Congrats, Jingsong!
> > > > >   
> > > > >On 13.06.22 08:58,
> > Becket
> > > > Qin wrote:
> > > > >Hi all,
> > > > >   
> > > > >I'm very happy
> to
> > > > announce that Jingsong Lee has joined the
> > > > >Flink
> > > > >PMC!
> > > > >   
> > > > >Jingsong became
> a
> > > > Flink committer in Feb 2020 and has been
> > > > >continuously
> > > > >contributing to
> > the
> > > > 

Re: [VOTE] FLIP-224: Blocklist Mechanism

[Peter Huang]

+1

On Wed, Jun 15, 2022 at 2:55 AM Xintong Song  wrote:

> +1 (binding)
>
> Best,
>
> Xintong
>
>
>
> On Wed, Jun 15, 2022 at 5:30 PM Jiangang Liu 
> wrote:
>
> > +1
> >
> > Chesnay Schepler  于2022年6月15日周三 17:15写道：
> >
> > > +1
> > >
> > > On 15/06/2022 10:49, Lijie Wang wrote:
> > > > Hi everyone,
> > > >
> > > > We've received some additional concerns since the last vote [1], and
> > > > therefore made a lot of changes to design.  You can find the details
> in
> > > [2]
> > > > and the discussions in [3].
> > > >
> > > > Now I'd like to start a new vote thread for FLIP-224. The vote will
> > last
> > > > for at least 72 hours unless there is an objection or insufficient
> > votes.
> > > >
> > > > [1] https://lists.apache.org/thread/3416vks1j35co9608gkmsoplvcjjz7bg
> > > > [2] https://cwiki.apache.org/confluence/display/FLINK/FLIP-224
> > > > %3A+Blocklist+Mechanism
> > > > [3] https://lists.apache.org/thread/fngkk52kjbc6b6v9nn0lkfq6hhsbgb1h
> > > > Best,
> > > > Lijie
> > > >
> > >
> > >
> >
>

[jira] [Created] (FLINK-28081) Remove deprecated Hadoop specific Flink configuration options

[Gabor Somogyi (Jira)]

Gabor Somogyi created FLINK-28081:
-

 Summary: Remove deprecated Hadoop specific Flink configuration 
options
 Key: FLINK-28081
 URL: https://issues.apache.org/jira/browse/FLINK-28081
 Project: Flink
  Issue Type: Sub-task
  Components: Connectors / Hadoop Compatibility
Affects Versions: 1.16.0
Reporter: Gabor Somogyi


FLINK-7967 deprecated the following Flink configuration options in 1.5:
{code:java}
fs.hdfs.hdfsdefault
fs.hdfs.hdfssite
fs.hdfs.hadoopconf
{code}
These are deprecated for 10 minor releases so I think it's time to remove them.




--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Created] (FLINK-28080) Introduce MutableURLClassLoader as parent class of FlinkUserClassLoader and SafetyNetWrapperClassLoader

[dalongliu (Jira)]

dalongliu created FLINK-28080:
-

 Summary: Introduce MutableURLClassLoader as parent class of 
FlinkUserClassLoader and SafetyNetWrapperClassLoader
 Key: FLINK-28080
 URL: https://issues.apache.org/jira/browse/FLINK-28080
 Project: Flink
  Issue Type: Sub-task
  Components: Runtime / Task
Affects Versions: 1.16.0
Reporter: dalongliu
 Fix For: 1.16.0






--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Re: [DISCUSS ] Make state.backend.incremental as true by default

[Feifan Wang]

Thanks for bringing this up.
Strongly +1




——
Name: Feifan Wang
Email: zoltar9...@163.com


 Replied Message 
| From | Yuan Mei |
| Date | 06/15/2022 11:41 |
| To | dev ,
 |
| Subject | Re: [DISCUSS ] Make state.backend.incremental as true by default |
Thanks for bringing this up.

I am +1 on making incremental checkpoints by default for RocksDB, but not
universally for all state backends.

Besides being widely used in prod, enabling incremental checkpoint for
RocksDB by default is also a pre-requisite when enabling task-local by
default FLINK-15507 

The incremental checkpoint for the hashmap statebackend is under review
right now. CC @ro...@ververica.com  , which is not a
good idea being enabled by default in the first version.

Best,

Yuan

On Tue, Jun 14, 2022 at 7:33 PM Jiangang Liu 
wrote:

+1 for the suggestion. We have use the incremental checkpoint in our
production for a long time.

Hangxiang Yu  于2022年6月14日周二 15:41写道：

+1
It's basically enabled in most scenarios in production environments.
For HashMapStateBackend, it will adopt a full checkpoint even if we
enable
incremental checkpoint. It will also support incremental checkpoint after
[1]. It's compatible.
BTW, I think we may also need to improve the documentation of incremental
checkpoints which users usually ask. There are some tickets like [2][3].

Best,
Hangxiang.

[1] https://issues.apache.org/jira/browse/FLINK-21648
[2] https://issues.apache.org/jira/browse/FLINK-22797
[3] https://issues.apache.org/jira/browse/FLINK-7449

On Mon, Jun 13, 2022 at 7:48 PM Rui Fan <1996fan...@gmail.com> wrote:

Strongly +1

Best,
Rui Fan

On Mon, Jun 13, 2022 at 7:35 PM Martijn Visser <
martijnvis...@apache.org

wrote:

BTW, from my knowledge, nothing would happen for
HashMapStateBackend,
which does not support incremental checkpoint yet, when enabling
incremental checkpoints.

Thanks Yun, if no errors would occur then definitely +1 to enable it
by
default

Op ma 13 jun. 2022 om 12:42 schreef Alexander Fedulov <
alexan...@ververica.com>:

+1

From my experience, it is actually hard to come up with use cases
where
incremental checkpoints should explicitly not be enabled with the
RocksDB
state backend. If the state is so small that the full snapshots do
not
have any negative impact, one should consider using
HashMapStateBackend
anyway.

Best,
Alexander Fedulov


On Mon, Jun 13, 2022 at 12:26 PM Jing Ge 
wrote:

+1

Glad to see the kickoff of this discussion. Thanks Lihe for
driving
this!

We have actually already discussed it internally a few months
ago.
After
considering some corner cases, all agreed on enabling the
incremental
checkpoint as default.

Best regards,
Jing

On Mon, Jun 13, 2022 at 12:17 PM Yun Tang 
wrote:

Strongly +1 for making incremental checkpoints as default. Many
users
have
ever been asking why this configuration is not enabled by
default.

BTW, from my knowledge, nothing would happen for
HashMapStateBackend,
which does not support incremental checkpoint yet, when
enabling
incremental checkpoints.


Best
Yun Tang

From: Martijn Visser 
Sent: Monday, June 13, 2022 18:05
To: dev@flink.apache.org 
Subject: Re: [DISCUSS ] Make state.backend.incremental as true
by
default

Hi Lihe,

What happens if we enable incremental checkpoints by default
while
the
used
memory backend is HashMapStateBackend, which doesn't support
incremental
checkpoints?

Best regards,

Martijn

Op ma 13 jun. 2022 om 11:59 schreef Lihe Ma :

Hi, Everyone,

I would like to open a discussion on setting incremental
checkpoint
as
default behavior.

Currently, the configuration of state.backend.incremental is
set
as
false
by default. Incremental checkpoint has been adopted widely in
industry
community for many years , and it is also well-tested from
the
feedback
in
the community discussion. Incremental checkpointing is more
light-weighted:
shorter checkpoint duration, less uploaded data and less
resource
consumption.

In terms of backward compatibility, enable incremental
checkpointing
would
not make any data loss no matter restoring from a full
checkpoint/savepoint
or an incremental checkpoint.

FLIP-193 (Snapshot ownership)[1] has been released in 1.15,
incremental
checkpoint no longer depends on a previous restored
checkpoint
in
default
NO_CLAIM mode, which makes the checkpoint lineage much
cleaner,
it
is a
good chance to change the configuration
state.backend.incremental
to
true
as default.

Thus, based on the above discussion, I suggest to make
state.backend.incremental as true by default. What do you
think
of
this
proposal?

[1]







https://cwiki.apache.org/confluence/display/FLINK/FLIP-193%3A+Snapshots+ownership

Best regards,
Lihe Ma

[jira] [Created] (FLINK-28079) Check Hive DDL against table store schema when creating table

[Caizhi Weng (Jira)]

Caizhi Weng created FLINK-28079:
---

 Summary: Check Hive DDL against table store schema when creating 
table
 Key: FLINK-28079
 URL: https://issues.apache.org/jira/browse/FLINK-28079
 Project: Flink
  Issue Type: Sub-task
  Components: Table Store
Affects Versions: table-store-0.2.0
Reporter: Caizhi Weng


As table store schema is supported, we should use this schema as the ground 
truth. Hive DDL should only be used for checking.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Re: [VOTE] FLIP-224: Blocklist Mechanism

[Xintong Song]

+1 (binding)

Best,

Xintong



On Wed, Jun 15, 2022 at 5:30 PM Jiangang Liu 
wrote:

> +1
>
> Chesnay Schepler  于2022年6月15日周三 17:15写道：
>
> > +1
> >
> > On 15/06/2022 10:49, Lijie Wang wrote:
> > > Hi everyone,
> > >
> > > We've received some additional concerns since the last vote [1], and
> > > therefore made a lot of changes to design.  You can find the details in
> > [2]
> > > and the discussions in [3].
> > >
> > > Now I'd like to start a new vote thread for FLIP-224. The vote will
> last
> > > for at least 72 hours unless there is an objection or insufficient
> votes.
> > >
> > > [1] https://lists.apache.org/thread/3416vks1j35co9608gkmsoplvcjjz7bg
> > > [2] https://cwiki.apache.org/confluence/display/FLINK/FLIP-224
> > > %3A+Blocklist+Mechanism
> > > [3] https://lists.apache.org/thread/fngkk52kjbc6b6v9nn0lkfq6hhsbgb1h
> > > Best,
> > > Lijie
> > >
> >
> >
>

Re: [DISCUSS] Releasing 1.15.1

[David Anderson]

I'm now thinking we should delay 1.15.1 long enough to see if we can
include a fix for FLINK-28060 [1], which is a serious regression affecting
several Kafka users.

[1] https://issues.apache.org/jira/browse/FLINK-28060

On Fri, Jun 10, 2022 at 12:15 PM David Anderson 
wrote:

> Since no one has brought up any blockers, I'll plan to start the release
> process on Monday unless I hear otherwise.
>
> Best,
> David
>
> On Thu, Jun 9, 2022 at 10:20 AM Yun Gao 
> wrote:
>
>> Hi David,
>>
>> Very thanks for driving the new version, also +1 since we already
>> accumulated some fixes.
>>
>> Regarding https://issues.apache.org/jira/browse/FLINK-27492, currently
>> there are still some
>> controversy with how to deal with the artifacts. I also agree we may not
>> hold up the release
>> with this issue. We'll try to reach to the consensus as soon as possible
>> to try best catching
>> up with the release.
>>
>> Best,
>> Yun
>>
>>
>>
>> --
>> From:LuNing Wang 
>> Send Time:2022 Jun. 9 (Thu.) 10:10
>> To:dev 
>> Subject:Re: [DISCUSS] Releasing 1.15.1
>>
>> Hi David,
>>
>> +1
>> Thank you for driving this.
>>
>> Best regards,
>> LuNing Wang
>>
>> Jing Ge  于2022年6月8日周三 20:45写道：
>>
>> > +1
>> >
>> > Thanks David for driving it!
>> >
>> > Best regards,
>> > Jing
>> >
>> >
>> > On Wed, Jun 8, 2022 at 2:32 PM Xingbo Huang  wrote:
>> >
>> > > Hi David,
>> > >
>> > > +1
>> > > Thank you for driving this.
>> > >
>> > > Best,
>> > > Xingbo
>> > >
>> > > Chesnay Schepler  于2022年6月8日周三 18:41写道：
>> > >
>> > > > +1
>> > > >
>> > > > Thank you for proposing this. I can take care of the PMC-side of
>> > things.
>> > > >
>> > > > On 08/06/2022 12:37, Jingsong Li wrote:
>> > > > > +1
>> > > > >
>> > > > > Thanks David for volunteering to manage the release.
>> > > > >
>> > > > > Best,
>> > > > > Jingsong
>> > > > >
>> > > > > On Wed, Jun 8, 2022 at 6:21 PM Jark Wu  wrote:
>> > > > >> Hi David, thank you for driving the release.
>> > > > >>
>> > > > >> +1 for the 1.15.1 release. The release-1.15 branch
>> > > > >> already contains many bug fixes and some SQL
>> > > > >> issues are quite critical.
>> > > > >>
>> > > > >> Btw, FLINK-27606 has been merged just now.
>> > > > >>
>> > > > >> Best,
>> > > > >> Jark
>> > > > >>
>> > > > >>
>> > > > >> On Wed, 8 Jun 2022 at 17:40, David Anderson <
>> dander...@apache.org>
>> > > > wrote:
>> > > > >>
>> > > > >>> I would like to start a discussion on releasing 1.15.1. Flink
>> 1.15
>> > > was
>> > > > >>> released on the 5th of May [1] and so far 43 issues have been
>> > > resolved,
>> > > > >>> including several user-facing issues with blocker and critical
>> > > > priorities
>> > > > >>> [2]. (The recent problem with FileSink rolling policies not
>> working
>> > > > >>> properly in 1.15.0 got me thinking it might be time for bug-fix
>> > > > release.)
>> > > > >>>
>> > > > >>> There currently remain 16 unresolved tickets with a fixVersion
>> of
>> > > > 1.15.1
>> > > > >>> [3], five of which are about CI infrastructure and tests. There
>> is
>> > > > only one
>> > > > >>> such ticket marked Critical:
>> > > > >>>
>> > > > >>> https://issues.apache.org/jira/browse/FLINK-27492 Flink table
>> > scala
>> > > > >>> example
>> > > > >>> does not including the scala-api jars
>> > > > >>>
>> > > > >>> I'm not convinced we should hold up a release for this issue,
>> but
>> > on
>> > > > the
>> > > > >>> other hand, it seems that this issue can be resolved by making a
>> > > > decision
>> > > > >>> about how to handle the missing dependencies. @Timo Walther
>> > > > >>>  @yun_gao can you give an update?
>> > > > >>>
>> > > > >>> Two other open issues seem to have made significant progress
>> > (listed
>> > > > >>> below). Would it make sense to wait for either of these? Are
>> there
>> > > any
>> > > > >>> other open tickets we should consider waiting for?
>> > > > >>>
>> > > > >>> https://issues.apache.org/jira/browse/FLINK-27420 Suspended
>> > > > SlotManager
>> > > > >>> fail to reregister metrics when started again
>> > > > >>> https://issues.apache.org/jira/browse/FLINK-27606
>> CompileException
>> > > > when
>> > > > >>> using UDAF with merge() method
>> > > > >>>
>> > > > >>> I would volunteer to manage the release. Is there a PMC member
>> who
>> > > > would
>> > > > >>> join me to help, as needed?
>> > > > >>>
>> > > > >>> Best,
>> > > > >>> David
>> > > > >>>
>> > > > >>> [1]
>> > https://flink.apache.org/news/2022/05/05/1.15-announcement.html
>> > > > >>>
>> > > > >>> [2]
>> > > > >>>
>> > > > >>>
>> > > >
>> > >
>> >
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20status%20in%20%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%201.15.1%20ORDER%20BY%20priority%20DESC%2C%20created%20DESC
>> > > > >>>
>> > > > >>> [3]
>> > > > >>>
>> > > > >>>
>> > > >
>> > >
>> >
>> 

Re: [VOTE] FLIP-224: Blocklist Mechanism

[Jiangang Liu]

+1

Chesnay Schepler  于2022年6月15日周三 17:15写道：

> +1
>
> On 15/06/2022 10:49, Lijie Wang wrote:
> > Hi everyone,
> >
> > We've received some additional concerns since the last vote [1], and
> > therefore made a lot of changes to design.  You can find the details in
> [2]
> > and the discussions in [3].
> >
> > Now I'd like to start a new vote thread for FLIP-224. The vote will last
> > for at least 72 hours unless there is an objection or insufficient votes.
> >
> > [1] https://lists.apache.org/thread/3416vks1j35co9608gkmsoplvcjjz7bg
> > [2] https://cwiki.apache.org/confluence/display/FLINK/FLIP-224
> > %3A+Blocklist+Mechanism
> > [3] https://lists.apache.org/thread/fngkk52kjbc6b6v9nn0lkfq6hhsbgb1h
> > Best,
> > Lijie
> >
>
>

[jira] [Created] (FLINK-28078) ZooKeeperMultipleComponentLeaderElectionDriverTest.testLeaderElectionWithMultipleDrivers runs into timeout

[Matthias Pohl (Jira)]

Matthias Pohl created FLINK-28078:
-

 Summary: 
ZooKeeperMultipleComponentLeaderElectionDriverTest.testLeaderElectionWithMultipleDrivers
 runs into timeout
 Key: FLINK-28078
 URL: https://issues.apache.org/jira/browse/FLINK-28078
 Project: Flink
  Issue Type: Bug
Affects Versions: 1.16.0
Reporter: Matthias Pohl


I am observing multiple fails where the CI seems to be getting stuck and fails 
because of running into the timeout. 

[Build 
#36259|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=36259=logs=5c8e7682-d68f-54d1-16a2-a09310218a49=86f654fa-ab48-5c1a-25f4-7e7f6afb9bba=12054]
 got stuck in a {{StreamFaultToleranceTestBase}} subclass

[Build 
#36209|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=36209=logs=a57e0635-3fad-5b08-57c7-a4142d7d6fa9=2ef0effc-1da1-50e5-c2bd-aab434b1c5b7=9370]
 got stuck in {{KeyedStateCheckpointingITCase.testWithMemoryBackendSync}}

[Build 
#36189|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=36189=logs=0da23115-68bb-5dcd-192c-bd4c8adebde1=24c3384f-1bcb-57b3-224f-51bf973bbee8=10455]
 got stuck in 
{{ZooKeeperMultipleComponentLeaderElectionDriverTest.testLeaderElectionWithMultipleDrivers}}

 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Created] (FLINK-28077) KeyedStateCheckpointingITCase.testWithMemoryBackendSync runs into timeout

[Matthias Pohl (Jira)]

Matthias Pohl created FLINK-28077:
-

 Summary: KeyedStateCheckpointingITCase.testWithMemoryBackendSync 
runs into timeout
 Key: FLINK-28077
 URL: https://issues.apache.org/jira/browse/FLINK-28077
 Project: Flink
  Issue Type: Bug
Affects Versions: 1.16.0
Reporter: Matthias Pohl


I am observing multiple fails where the CI seems to be getting stuck and fails 
because of running into the timeout. 

[Build 
#36259|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=36259=logs=5c8e7682-d68f-54d1-16a2-a09310218a49=86f654fa-ab48-5c1a-25f4-7e7f6afb9bba=12054]
 got stuck in a {{StreamFaultToleranceTestBase}} subclass

[Build 
#36209|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=36209=logs=a57e0635-3fad-5b08-57c7-a4142d7d6fa9=2ef0effc-1da1-50e5-c2bd-aab434b1c5b7=9370]
 got stuck in {{KeyedStateCheckpointingITCase.testWithMemoryBackendSync}}

[Build 
#36189|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=36189=logs=0da23115-68bb-5dcd-192c-bd4c8adebde1=24c3384f-1bcb-57b3-224f-51bf973bbee8=10455]
 got stuck in 
{{ZooKeeperMultipleComponentLeaderElectionDriverTest.testLeaderElectionWithMultipleDrivers}}

 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Created] (FLINK-28076) CI runs keep getting stuck

[Matthias Pohl (Jira)]

Matthias Pohl created FLINK-28076:
-

 Summary: CI runs keep getting stuck
 Key: FLINK-28076
 URL: https://issues.apache.org/jira/browse/FLINK-28076
 Project: Flink
  Issue Type: Bug
Affects Versions: 1.16.0
Reporter: Matthias Pohl


I am observing multiple fails where the CI seems to be getting stuck and fails 
because of running into the timeout. 

[Build 
#36259|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=36259=logs=5c8e7682-d68f-54d1-16a2-a09310218a49=86f654fa-ab48-5c1a-25f4-7e7f6afb9bba=12054]
 got stuck in a {{StreamFaultToleranceTestBase}} subclass

[Build 
#36209|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=36209=logs=a57e0635-3fad-5b08-57c7-a4142d7d6fa9=2ef0effc-1da1-50e5-c2bd-aab434b1c5b7=9370]
 got stuck in {{KeyedStateCheckpointingITCase.testWithMemoryBackendSync}}

[Build 
#36189|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=36189=logs=0da23115-68bb-5dcd-192c-bd4c8adebde1=24c3384f-1bcb-57b3-224f-51bf973bbee8=10455]
 got stuck in 
{{ZooKeeperMultipleComponentLeaderElectionDriverTest.testLeaderElectionWithMultipleDrivers}}

 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Re: [VOTE] FLIP-224: Blocklist Mechanism

[Chesnay Schepler]

+1

On 15/06/2022 10:49, Lijie Wang wrote:

Hi everyone,

We've received some additional concerns since the last vote [1], and
therefore made a lot of changes to design.  You can find the details in [2]
and the discussions in [3].

Now I'd like to start a new vote thread for FLIP-224. The vote will last
for at least 72 hours unless there is an objection or insufficient votes.

[1] https://lists.apache.org/thread/3416vks1j35co9608gkmsoplvcjjz7bg
[2] https://cwiki.apache.org/confluence/display/FLINK/FLIP-224
%3A+Blocklist+Mechanism
[3] https://lists.apache.org/thread/fngkk52kjbc6b6v9nn0lkfq6hhsbgb1h
Best,
Lijie

[jira] [Created] (FLINK-28075) get statistics for partitioned table even without partition pruning

[godfrey he (Jira)]

godfrey he created FLINK-28075:
--

 Summary: get statistics for partitioned table even without 
partition pruning
 Key: FLINK-28075
 URL: https://issues.apache.org/jira/browse/FLINK-28075
 Project: Flink
  Issue Type: New Feature
  Components: Table SQL / Planner
Reporter: godfrey he
 Fix For: 1.16.0


Currently, the statistics for partitioned table will not be collected if there 
is no partition pruning



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Created] (FLINK-28074) display

[godfrey he (Jira)]

godfrey he created FLINK-28074:
--

 Summary: display
 Key: FLINK-28074
 URL: https://issues.apache.org/jira/browse/FLINK-28074
 Project: Flink
  Issue Type: New Feature
Reporter: godfrey he






--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[VOTE] FLIP-224: Blocklist Mechanism

[Lijie Wang]

Hi everyone,

We've received some additional concerns since the last vote [1], and
therefore made a lot of changes to design.  You can find the details in [2]
and the discussions in [3].

Now I'd like to start a new vote thread for FLIP-224. The vote will last
for at least 72 hours unless there is an objection or insufficient votes.

[1] https://lists.apache.org/thread/3416vks1j35co9608gkmsoplvcjjz7bg
[2] https://cwiki.apache.org/confluence/display/FLINK/FLIP-224
%3A+Blocklist+Mechanism
[3] https://lists.apache.org/thread/fngkk52kjbc6b6v9nn0lkfq6hhsbgb1h
Best,
Lijie

Re: [DISCUSS] FLIP-224: Blacklist Mechanism

[Lijie Wang]

Thanks Chesnay & Zhu.

I will start a new vote thread soon.

Best,
Lijie

Chesnay Schepler  于2022年6月15日周三 15:49写道：

> To expand a bit for transparency, Zhu Zhu and I had long discussion
> (literally spanning days) about this FLIP and it's relation to
> speculative execution.
>
> The gist of it is that speculative execution doesn't strictly need the
> block list; just _some_ mechanism to select/request slots from other nodes.
> It is however at this time the easiest way to implement it because of
> the technical debt we have in the scheduler components (e.g., adaptive
> scheduler not being used for all streaming jobs or default scheduler not
> being integrated fully into declarative resource management).
> Because of that I was worried that we might expand the API now to unlock
> speculative execution, but then end up not actually requiring it down
> the line (but still being stuck with it).
> This should give us quite a bit more freedom as to how we implement it.
> Which is particularly important because we already identified some
> limitations in the current design (e.g., blocks not being scoped to
> jobs, resourceID-based blocks intefeing with hard-coded resource IDs,
> potentially blocking more slots than necessary).
>
> Shall we start a new vote thread, since the design changed quite a bit?
>
> On 15/06/2022 09:33, Zhu Zhu wrote:
> > Hi everyone,
> > Thank you all for the feedback!
> >
> > We receive concerns that the blocklist feature is not strongly
> > required except for the needs of speculative execution. So as the
> > first step, we will limit the scope of FLIP-224 to only support
> > speculative execution, and therefore, not add public interfaces for
> > users to manipulate with the blocklist directly.
> >
> > If later we receive strong requirements for blocklist from users, we
> > will have another FLIP to open it to users with well designed public
> > interfaces and web UI.
> >
> > Thanks,
> > Zhu
> >
> > Zhu Zhu  于2022年6月10日周五 18:45写道：
> >> 1) With the declarative slot allocation protocol, it's not easy to
> >> keep the slow slots which may have satisfy the slot request already,
> >> but ask for more slots from the resource manager.
> >> And we are also concerned to use detected slow slots, which may add
> >> load to the slow nodes and further slow down the tasks on the slow
> >> nodes. Because we found slow nodes are mostly caused by heavy loads.
> >>
> >> 2) I see your point. The blocker here is that batch jobs currently
> >> uses DefaultScheduler. The scheduler does not see slots directly and
> >> does not know which of them are from slow nodes, so it's hard for it
> >> to rescale the vertex according to this information. Besides that, it
> >> cannot help with the stage that first observed and affected the slow
> >> nodes.
> >>
> >> Thanks,
> >> Zhu
> >>
> >> Chesnay Schepler  于2022年6月10日周五 17:04写道：
> >>> 1)
> >>> It's true that if we handle this entirely in the scheduler we may get
> a bunch of slow slots from the RM.
> >>> My point is that this isn't necessarily a problem; it depends on how
> you handle those slots.
> >>>
> >>> We anyway need to account for the possibility that we're not getting
> any new fast slots from the RM.
> >>> With that in mind, I'd rather not categorically throw away the slow
> slots we got, but try to make use of them somehow.
> >>>
> >>> 2)
> >>> The idea was to rescale the job when the current stage finishes.
> >>> The speculative execution handles slow nodes being detected in the
> current stage,
> >>> next stage we use _some_ strategy to handle slow nodes (be it ignoring
> those, rescaling the job, ...).
> >>>
> >>> 3)
> >>> It's a fair observation that once you push this to the RM you end up
> with a de-facto blocklist :)
> >>>
> >>> On 08/06/2022 17:11, Zhu Zhu wrote:
> >>>
> >>> Thanks Chesnay for the feedback in the vote thread.
> >>> (https://lists.apache.org/thread/opc7jg3rpxnwotkb0fcn4wnm02m4397o)
> >>>
> >>> I'd like to continue the discussion in this thread so that the
> >>> discussions can be better tracked.
> >>>
> >>> Regarding your questions, here are my thoughts:
> >>> 1. The current locality mechanism does not work well to avoid
> >>> deploying tasks to slow nodes because it cannot proactively reject or
> >>> release slots from the slow nodes. And it cannot help at the resource
> >>> manager side to avoid allocating free slots or launching new
> >>> TaskManagers on slow nodes.
> >>> 2. Dynamically downscaling or upscaling a batch job is usually
> >>> unacceptable because it means to re-run the whole stage.
> >>> 3. Extending the requirement declaration to have a notion of
> >>> "undesirable nodes" is an option. And it is actually how we started.
> >>> Considering implementation details, we found we need that
> >>> - a tracker to collect all the undesirable(detected slow nodes)
> >>> - to filter out slots from undesirable nodes when allocating slots
> >>> from the SlotPool
> >>> - ask the ResourceManager for slots that are not on the 

Re: Re: [DISCUSS] FLIP-240: Introduce "ANALYZE TABLE" Syntax

[godfrey he]

Hi Jark,

Thanks for the inputs.

>Do we need to provide DESC EXTENDED  statement like Spark[1] to
>show statistic for table/partition/columns?
We do have supported `DESC EXTENDED` syntax, but currently only table schema
will be display, I think we just need a JIRA to support it.

> is it possible to ignore execution mode and force using batch mode for the 
> statement?
As I replied above, The semantics of `ANALYZE TABLE` does not
distinguish batch and streaming,
It works for both batch and streaming, but the result of unbounded
sources is meaningless.
Currently, I throw exception for streaming mode,
and we can support streaming mode with bounded source in the future.

Best,
Godfrey

Jark Wu  于2022年6月14日周二 17:56写道：
>
> Hi Godfrey, thanks for starting this discussion, this is a great feature
> for batch users.
>
> The FLIP looks good to me in general.
>
> I only have 2 comments:
>
> 1) How do users know whether the given table or partition contains required
> statistics?
> Do we need to provide DESC EXTENDED  statement like Spark[1] to
> show statistic for table/partition/columns?
>
> 2) If ANALYZE TABLE can only run in batch mode, is it possible to ignore
> execution mode
> and force using batch mode for the statement? From my perspective, ANALYZE
> TABLE
> is an auxiliary statement similar to SHOW TABLES but heavier, which doesn't
> care about
> environment execution mode.
>
> Best,
> Jark
>
> [1]:
> https://spark.apache.org/docs/3.0.0-preview/sql-ref-syntax-aux-analyze-table.html
>
> On Tue, 14 Jun 2022 at 13:52, Jing Ge  wrote:
>
> > Hi 华宗
> >
> > 退订请发送任意消息至dev-unsubscr...@flink.apache.org
> > In order to unsubscribe, please send an email to
> > dev-unsubscr...@flink.apache.org
> >
> > Thanks
> >
> > Best regards,
> > Jing
> >
> >
> > On Tue, Jun 14, 2022 at 2:05 AM 华宗  wrote:
> >
> > > 退订
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > At 2022-06-13 22:44:24, "cao zou"  wrote:
> > > >Hi godfrey, thanks for your detail explanation.
> > > >After explaining and glancing over the FLIP-231, I think it is
> > > >really need, +1 for this and looking forward to it.
> > > >
> > > >best
> > > >zoucao
> > > >
> > > >godfrey he  于2022年6月13日周一 14:43写道：
> > > >
> > > >> Hi Ingo,
> > > >>
> > > >> The semantics does not distinguish batch and streaming,
> > > >> It works for both batch and streaming, but the result of
> > > >> unbounded sources is meaningless.
> > > >> Currently, I throw exception for streaming mode,
> > > >> and we can support streaming mode with bounded source
> > > >> in the future.
> > > >>
> > > >> Best,
> > > >> Godfrey
> > > >>
> > > >> Ingo Bürk  于2022年6月13日周一 14:17写道：
> > > >> >
> > > >> > Hi Godfrey,
> > > >> >
> > > >> > thank you for the explanation. A SELECT is definitely more generic
> > and
> > > >> > will work for all connectors automatically. As such I think it's a
> > > good
> > > >> > baseline solution regardless.
> > > >> >
> > > >> > We can also think about allowing connector-specific optimizations in
> > > the
> > > >> > future, but I do like your idea of letting the optimizer rules
> > > perform a
> > > >> > lot of the work here already by leveraging existing optimizations.
> > > >> > Similarly things like non-null counts of non-nullable columns would
> > > (or
> > > >> > at least could) be handled by the optimizer rules already.
> > > >> >
> > > >> > So as far as that point goes, +1 to the generic approach.
> > > >> >
> > > >> > One more point, though: In general we should avoid supporting
> > features
> > > >> > only in specific modes as it breaks the unification promise. Given
> > > that
> > > >> > ANALYZE is a manual and completely optional operation I'm OK with
> > > doing
> > > >> > that here in principle. However, I wonder what will happen in the
> > > >> > streaming / unbounded case. Do you plan to throw an error? Or do we
> > > >> > complete the command as successful but without doing anything?
> > > >> >
> > > >> >
> > > >> > Best
> > > >> > Ingo
> > > >> >
> > > >> > On 13.06.22 05:50, godfrey he wrote:
> > > >> > > Hi Ingo,
> > > >> > >
> > > >> > > Thanks for the inputs.
> > > >> > >
> > > >> > > I think converting `ANALYZE TABLE` to `SELECT` statement is
> > > >> > > more generic approach. Because query plan optimization is more
> > > generic,
> > > >> > >   we can provide more optimization rules to optimize not only
> > > `SELECT`
> > > >> statement
> > > >> > > converted from `ANALYZE TABLE` but also the `SELECT` statement
> > > written
> > > >> by users.
> > > >> > >
> > > >> > >> JDBC connector can get a row count estimate without performing a
> > > >> > >> SELECT COUNT(1)
> > > >> > > To optimize such cases, we can implement a rule to push aggregate
> > > into
> > > >> > > table source.
> > > >> > > Currently, there is a similar rule: SupportsAggregatePushDown,
> > which
> > > >> > > supports only pushing
> > > >> > > local aggregate into source now.
> > > >> > >
> > > >> > >
> > > >> > > Best,
> > > 

Re: [DISCUSS] FLIP-224: Blacklist Mechanism

[Chesnay Schepler]

To expand a bit for transparency, Zhu Zhu and I had long discussion 
(literally spanning days) about this FLIP and it's relation to 
speculative execution.


The gist of it is that speculative execution doesn't strictly need the 
block list; just _some_ mechanism to select/request slots from other nodes.
It is however at this time the easiest way to implement it because of 
the technical debt we have in the scheduler components (e.g., adaptive 
scheduler not being used for all streaming jobs or default scheduler not 
being integrated fully into declarative resource management).
Because of that I was worried that we might expand the API now to unlock 
speculative execution, but then end up not actually requiring it down 
the line (but still being stuck with it).

This should give us quite a bit more freedom as to how we implement it.
Which is particularly important because we already identified some 
limitations in the current design (e.g., blocks not being scoped to 
jobs, resourceID-based blocks intefeing with hard-coded resource IDs, 
potentially blocking more slots than necessary).


Shall we start a new vote thread, since the design changed quite a bit?

On 15/06/2022 09:33, Zhu Zhu wrote:

Hi everyone,
Thank you all for the feedback!

We receive concerns that the blocklist feature is not strongly
required except for the needs of speculative execution. So as the
first step, we will limit the scope of FLIP-224 to only support
speculative execution, and therefore, not add public interfaces for
users to manipulate with the blocklist directly.

If later we receive strong requirements for blocklist from users, we
will have another FLIP to open it to users with well designed public
interfaces and web UI.

Thanks,
Zhu

Zhu Zhu  于2022年6月10日周五 18:45写道：

1) With the declarative slot allocation protocol, it's not easy to
keep the slow slots which may have satisfy the slot request already,
but ask for more slots from the resource manager.
And we are also concerned to use detected slow slots, which may add
load to the slow nodes and further slow down the tasks on the slow
nodes. Because we found slow nodes are mostly caused by heavy loads.

2) I see your point. The blocker here is that batch jobs currently
uses DefaultScheduler. The scheduler does not see slots directly and
does not know which of them are from slow nodes, so it's hard for it
to rescale the vertex according to this information. Besides that, it
cannot help with the stage that first observed and affected the slow
nodes.

Thanks,
Zhu

Chesnay Schepler  于2022年6月10日周五 17:04写道：

1)
It's true that if we handle this entirely in the scheduler we may get a bunch 
of slow slots from the RM.
My point is that this isn't necessarily a problem; it depends on how you handle 
those slots.

We anyway need to account for the possibility that we're not getting any new 
fast slots from the RM.
With that in mind, I'd rather not categorically throw away the slow slots we 
got, but try to make use of them somehow.

2)
The idea was to rescale the job when the current stage finishes.
The speculative execution handles slow nodes being detected in the current 
stage,
next stage we use _some_ strategy to handle slow nodes (be it ignoring those, 
rescaling the job, ...).

3)
It's a fair observation that once you push this to the RM you end up with a 
de-facto blocklist :)

On 08/06/2022 17:11, Zhu Zhu wrote:

Thanks Chesnay for the feedback in the vote thread.
(https://lists.apache.org/thread/opc7jg3rpxnwotkb0fcn4wnm02m4397o)

I'd like to continue the discussion in this thread so that the
discussions can be better tracked.

Regarding your questions, here are my thoughts:
1. The current locality mechanism does not work well to avoid
deploying tasks to slow nodes because it cannot proactively reject or
release slots from the slow nodes. And it cannot help at the resource
manager side to avoid allocating free slots or launching new
TaskManagers on slow nodes.
2. Dynamically downscaling or upscaling a batch job is usually
unacceptable because it means to re-run the whole stage.
3. Extending the requirement declaration to have a notion of
"undesirable nodes" is an option. And it is actually how we started.
Considering implementation details, we found we need that
- a tracker to collect all the undesirable(detected slow nodes)
- to filter out slots from undesirable nodes when allocating slots
from the SlotPool
- ask the ResourceManager for slots that are not on the undesirable
nodes. The ResourceManager may further need to ask for new
TaskManagers that are not on the undesirable nodes.
Then, with all these functionality, we found that we almost have a
blocklist mechanism. As blocklist mechanism is a common concept and is
possible to benefit users, we took this chance to propose the
blocklist mechanism.
4. A cluster-wide shared blocklist is not a must for speculative
execution at the moment. It is mainly part of a standalone blocklist
feature to host user specified block items. To 

Re: [DISCUSS] FLIP-241: Completed Jobs Information Enhancement

[Xintong Song]

Thanks Junhan,

+1 for the proposed improvements.

Best,

Xintong



On Wed, Jun 15, 2022 at 3:16 PM Yangze Guo  wrote:

> Thanks for driving this, Junhan.
>
> I think it's a valuable usability improvement for both streaming and
> batch users. Looking forward to the community feedback.
>
> Best,
> Yangze Guo
>
>
>
> On Wed, Jun 15, 2022 at 3:10 PM junhan yang 
> wrote:
> >
> > Hi all,
> >
> > I would like to open a discussion on FLIP-241: Completed Jobs Information
> > Enhancement.
> >
> > As far as we can tell, streaming and batch users have different interests
> > in probing a job. As Flink grows into a unified streaming & batch
> processor
> > and is adopted by more and more batch users, the user experience of
> > completed job's inspection has become more and more important. After
> doing
> > several market research, there are several potential improvements
> spotted.
> >
> > The main purpose here is due to the involvement of WebUI & REST API
> > changes, which should be openly discussed and voted on as FLIPs.
> >
> > You can find more details in FLIP-241 document[1]. Looking forward to
> > your feedback.
> >
> > [1] https://cwiki.apache.org/confluence/x/dRD1D
> >
> > Best regards,
> > Junhan
>

Re: [DISCUSS] FLIP-224: Blacklist Mechanism

[Zhu Zhu]

Hi everyone,
Thank you all for the feedback!

We receive concerns that the blocklist feature is not strongly
required except for the needs of speculative execution. So as the
first step, we will limit the scope of FLIP-224 to only support
speculative execution, and therefore, not add public interfaces for
users to manipulate with the blocklist directly.

If later we receive strong requirements for blocklist from users, we
will have another FLIP to open it to users with well designed public
interfaces and web UI.

Thanks,
Zhu

Zhu Zhu  于2022年6月10日周五 18:45写道：
>
> 1) With the declarative slot allocation protocol, it's not easy to
> keep the slow slots which may have satisfy the slot request already,
> but ask for more slots from the resource manager.
> And we are also concerned to use detected slow slots, which may add
> load to the slow nodes and further slow down the tasks on the slow
> nodes. Because we found slow nodes are mostly caused by heavy loads.
>
> 2) I see your point. The blocker here is that batch jobs currently
> uses DefaultScheduler. The scheduler does not see slots directly and
> does not know which of them are from slow nodes, so it's hard for it
> to rescale the vertex according to this information. Besides that, it
> cannot help with the stage that first observed and affected the slow
> nodes.
>
> Thanks,
> Zhu
>
> Chesnay Schepler  于2022年6月10日周五 17:04写道：
> >
> > 1)
> > It's true that if we handle this entirely in the scheduler we may get a 
> > bunch of slow slots from the RM.
> > My point is that this isn't necessarily a problem; it depends on how you 
> > handle those slots.
> >
> > We anyway need to account for the possibility that we're not getting any 
> > new fast slots from the RM.
> > With that in mind, I'd rather not categorically throw away the slow slots 
> > we got, but try to make use of them somehow.
> >
> > 2)
> > The idea was to rescale the job when the current stage finishes.
> > The speculative execution handles slow nodes being detected in the current 
> > stage,
> > next stage we use _some_ strategy to handle slow nodes (be it ignoring 
> > those, rescaling the job, ...).
> >
> > 3)
> > It's a fair observation that once you push this to the RM you end up with a 
> > de-facto blocklist :)
> >
> > On 08/06/2022 17:11, Zhu Zhu wrote:
> >
> > Thanks Chesnay for the feedback in the vote thread.
> > (https://lists.apache.org/thread/opc7jg3rpxnwotkb0fcn4wnm02m4397o)
> >
> > I'd like to continue the discussion in this thread so that the
> > discussions can be better tracked.
> >
> > Regarding your questions, here are my thoughts:
> > 1. The current locality mechanism does not work well to avoid
> > deploying tasks to slow nodes because it cannot proactively reject or
> > release slots from the slow nodes. And it cannot help at the resource
> > manager side to avoid allocating free slots or launching new
> > TaskManagers on slow nodes.
> > 2. Dynamically downscaling or upscaling a batch job is usually
> > unacceptable because it means to re-run the whole stage.
> > 3. Extending the requirement declaration to have a notion of
> > "undesirable nodes" is an option. And it is actually how we started.
> > Considering implementation details, we found we need that
> > - a tracker to collect all the undesirable(detected slow nodes)
> > - to filter out slots from undesirable nodes when allocating slots
> > from the SlotPool
> > - ask the ResourceManager for slots that are not on the undesirable
> > nodes. The ResourceManager may further need to ask for new
> > TaskManagers that are not on the undesirable nodes.
> > Then, with all these functionality, we found that we almost have a
> > blocklist mechanism. As blocklist mechanism is a common concept and is
> > possible to benefit users, we took this chance to propose the
> > blocklist mechanism.
> > 4. A cluster-wide shared blocklist is not a must for speculative
> > execution at the moment. It is mainly part of a standalone blocklist
> > feature to host user specified block items. To avoid sharing job
> > specific blocked items between jobs, one way is to add a nullable
> > JobID tag for the blocked item.
> >
> > Thanks,
> > Zhu
> >
> > Zhu Zhu  于2022年6月7日周二 10:58写道：
> >
> > Hi Chesnay,
> >
> > Would you please take a look at the FLIP and discussion to see if all
> > your concerns have been addressed?
> >
> > Thanks,
> > Zhu
> >
> > Zhu Zhu  于2022年5月28日周六 13:26写道：
> >
> > Regarding the concern of the SlotManager, my two cents:
> > 1. it is necessary for the SlotManager to host blocked slots, in 2 cases:
> >   a. In standalone mode, a taskmanager may be temporarily added to
> > the blocklist. We do not want the TM to get disconnected and shut down.
> > So we need to keep its connection to RM and keep hosting its slots.
> >   b. When we want to avoid allocating slots to a slow nodes but do not
> > want to kill current running tasks on the nodes (MARK_BLOCKED mode).
> >
> > There is possible a way to keep the connection of a blocked task 

Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee

[Sergey Nuyanzin]

Congratulations, Jingsong!

On Wed, Jun 15, 2022 at 8:45 AM Jingsong Li  wrote:

> Thanks everyone.
>
> It's great to be with you in the Flink community!
>
> Best,
> Jingsong
>
> On Wed, Jun 15, 2022 at 2:11 PM Yun Gao 
> wrote:
> >
> > Congratulations, Jingsong!
> >
> > Best,
> > Yun Gao
> >
> >
> > --
> > From:Jing Zhang 
> > Send Time:2022 Jun. 14 (Tue.) 11:05
> > To:dev 
> > Subject:Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> >
> > Congratulations, Jingsong!
> >
> > Best,
> > Jing Zhang
> >
> > Leonard Xu  于2022年6月14日周二 10:54写道：
> >
> > > Congratulations, Jingsong!
> > >
> > >
> > > Best,
> > > Leonard
> > >
> > > > 2022年6月13日 下午6:52，刘首维  写道：
> > > >
> > > > Congratulations and well deserved, Jingsong!
> > > >
> > > >
> > > > Best regards,
> > > > Shouwei
> > > > --原始邮件--
> > > > 发件人:
> > > "dev"
> > >   <
> luoyu...@alumni.sjtu.edu.cn
> > > ;
> > > > 发送时间:2022年6月13日(星期一) 晚上6:09
> > > > 收件人:"dev"mailto:dev@flink.apache.org
> >;
> > > >
> > > > 主题:Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > > >
> > > >
> > > >
> > > > Congratulations, Jingsong!
> > > >
> > > >
> > > > Best regards,
> > > > Yuxia
> > > >
> > > > - 原始邮件 -
> > > > 发件人: "Yun Tang"  > > > 收件人: "dev"  > > > 发送时间: 星期一, 2022年 6 月 13日 下午 6:12:24
> > > > 主题: Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > > >
> > > > Congratulations, Jingsong! Well deserved.
> > > >
> > > > Best
> > > > Yun Tang
> > > > 
> > > > From: Xingbo Huang  > > > Sent: Monday, June 13, 2022 17:39
> > > > To: dev  > > > Subject: Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > > >
> > > > Congratulations, Jingsong!
> > > >
> > > > Best,
> > > > Xingbo
> > > >
> > > > Jane Chan  > > >
> > > >  Congratulations, Jingsong!
> > > > 
> > > >  Best,
> > > >  Jane Chan
> > > > 
> > > >  On Mon, Jun 13, 2022 at 4:43 PM Shuo Cheng  > >  wrote:
> > > > 
> > > >   Congratulations, Jingsong!
> > > >  
> > > >   On 6/13/22, Paul Lam  > > paullin3...@gmail.com> wrote:
> > > >Congrats, Jingsong! Well deserved!
> > > >   
> > > >Best,
> > > >Paul Lam
> > > >   
> > > >2022年6月13日 16:31，Lincoln Lee <
> lincoln.8...@gmail.com
> > >  写道：
> > > >   
> > > >Congratulations, Jingsong!
> > > >   
> > > >Best,
> > > >Lincoln Lee
> > > >   
> > > >   
> > > >Jark Wu  imj...@gmail.com>
> > > 于2022年6月13日周一 16:29写道：
> > > >   
> > > >Congrats, Jingsong!
> > > >   
> > > >Cheers,
> > > >Jark
> > > >   
> > > >On Mon, 13 Jun 2022 at 16:16, Jiangang Liu <
> > > >  liujiangangp...@gmail.com  >
> > > >wrote:
> > > >   
> > > >Congratulations, Jingsong!
> > > >   
> > > >Best,
> > > >Jiangang Liu
> > > >   
> > > >Martijn Visser  > >  于2022年6月13日周一 16:06写道：
> > > >   
> > > >Like everyone has mentioned, this is
> very
> > > well deserved.
> > > >Congratulations!
> > > >   
> > > >Op ma 13 jun. 2022 om 09:57 schreef
> > > Benchao Li <
> > > >  libenc...@apache.org 
> > > >   :
> > > >   
> > > >Congratulations, Jingsong!
> Well
> > > deserved.
> > > >   
> > > >Rui Fan <1996fan...@gmail.com
> > >  于2022年6月13日周一 15:53写道：
> > > >   
> > > >Congratulations, Jingsong!
> > > >   
> > > >Best,
> > > >Rui Fan
> > > >   
> > > >On Mon, Jun 13, 2022 at 3:40
> PM
> > > LuNing Wang <
> > > >  wang4lun...@gmail.com 
> > > >   
> > > >wrote:
> > > >   
> > > >Congratulations, Jingsong!
> > > >   
> > > >Best,
> > > >LuNing Wang
> > > >   
> > > >Ingo Bürk <
> > > airbla...@apache.org  于2022年6月13日周一
> > > 15:36写道：
> > > >   
> > > >Congrats, Jingsong!
> > > >   
> > > >On 13.06.22 08:58,
> Becket
> > > Qin wrote:
> > > >Hi all,
> > > >   
> > > >I'm very happy to
> > > announce that Jingsong Lee has joined the
> > > >Flink
> > > >PMC!
> > > >   
> > > >Jingsong became a
> > > Flink committer in Feb 2020 and has been
> > > >continuously
> > > >contributing to
> the
> > > project since then, mainly in Flink SQL.
> > > >He
> > > >has
> > > >been
> > > >quite active in
> the
> > > mailing list, fixing bugs, helping
> > > >verifying
> > > >releases,
> > > >reviewing patches
> and
> > > FLIPs. Jingsong is also devoted to
> > > >pushing
> > > >Flink
> > > >SQL
> > > >to new use cases.
> He
> > > spent a lot of time in implementing the
> > > >Flink
> > > >connectors for
> Apache
> > > Iceberg. Jingsong is also the primary
> > > >driver
> > > >behind
> > 

Re: [DISCUSS] FLIP-241: Completed Jobs Information Enhancement

[Yangze Guo]

Thanks for driving this, Junhan.

I think it's a valuable usability improvement for both streaming and
batch users. Looking forward to the community feedback.

Best,
Yangze Guo



On Wed, Jun 15, 2022 at 3:10 PM junhan yang  wrote:
>
> Hi all,
>
> I would like to open a discussion on FLIP-241: Completed Jobs Information
> Enhancement.
>
> As far as we can tell, streaming and batch users have different interests
> in probing a job. As Flink grows into a unified streaming & batch processor
> and is adopted by more and more batch users, the user experience of
> completed job's inspection has become more and more important. After doing
> several market research, there are several potential improvements spotted.
>
> The main purpose here is due to the involvement of WebUI & REST API
> changes, which should be openly discussed and voted on as FLIPs.
>
> You can find more details in FLIP-241 document[1]. Looking forward to
> your feedback.
>
> [1] https://cwiki.apache.org/confluence/x/dRD1D
>
> Best regards,
> Junhan

[DISCUSS] FLIP-241: Completed Jobs Information Enhancement

[junhan yang]

Hi all,

I would like to open a discussion on FLIP-241: Completed Jobs Information
Enhancement.

As far as we can tell, streaming and batch users have different interests
in probing a job. As Flink grows into a unified streaming & batch processor
and is adopted by more and more batch users, the user experience of
completed job's inspection has become more and more important. After doing
several market research, there are several potential improvements spotted.

The main purpose here is due to the involvement of WebUI & REST API
changes, which should be openly discussed and voted on as FLIPs.

You can find more details in FLIP-241 document[1]. Looking forward to
your feedback.

[1] https://cwiki.apache.org/confluence/x/dRD1D

Best regards,
Junhan

Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee

[Jingsong Li]

Thanks everyone.

It's great to be with you in the Flink community!

Best,
Jingsong

On Wed, Jun 15, 2022 at 2:11 PM Yun Gao  wrote:
>
> Congratulations, Jingsong!
>
> Best,
> Yun Gao
>
>
> --
> From:Jing Zhang 
> Send Time:2022 Jun. 14 (Tue.) 11:05
> To:dev 
> Subject:Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
>
> Congratulations, Jingsong!
>
> Best,
> Jing Zhang
>
> Leonard Xu  于2022年6月14日周二 10:54写道：
>
> > Congratulations, Jingsong!
> >
> >
> > Best,
> > Leonard
> >
> > > 2022年6月13日 下午6:52，刘首维  写道：
> > >
> > > Congratulations and well deserved, Jingsong!
> > >
> > >
> > > Best regards,
> > > Shouwei
> > > --原始邮件--
> > > 发件人:
> > "dev"
> >> ;
> > > 发送时间:2022年6月13日(星期一) 晚上6:09
> > > 收件人:"dev"mailto:dev@flink.apache.org>;
> > >
> > > 主题:Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > >
> > >
> > >
> > > Congratulations, Jingsong!
> > >
> > >
> > > Best regards,
> > > Yuxia
> > >
> > > - 原始邮件 -
> > > 发件人: "Yun Tang"  > > 收件人: "dev"  > > 发送时间: 星期一, 2022年 6 月 13日 下午 6:12:24
> > > 主题: Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > >
> > > Congratulations, Jingsong! Well deserved.
> > >
> > > Best
> > > Yun Tang
> > > 
> > > From: Xingbo Huang  > > Sent: Monday, June 13, 2022 17:39
> > > To: dev  > > Subject: Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > >
> > > Congratulations, Jingsong!
> > >
> > > Best,
> > > Xingbo
> > >
> > > Jane Chan  > >
> > >  Congratulations, Jingsong!
> > > 
> > >  Best,
> > >  Jane Chan
> > > 
> > >  On Mon, Jun 13, 2022 at 4:43 PM Shuo Cheng  >  wrote:
> > > 
> > >   Congratulations, Jingsong!
> > >  
> > >   On 6/13/22, Paul Lam  > paullin3...@gmail.com> wrote:
> > >Congrats, Jingsong! Well deserved!
> > >   
> > >Best,
> > >Paul Lam
> > >   
> > >2022年6月13日 16:31，Lincoln Lee  >  写道：
> > >   
> > >Congratulations, Jingsong!
> > >   
> > >Best,
> > >Lincoln Lee
> > >   
> > >   
> > >Jark Wu mailto:imj...@gmail.com>
> > 于2022年6月13日周一 16:29写道：
> > >   
> > >Congrats, Jingsong!
> > >   
> > >Cheers,
> > >Jark
> > >   
> > >On Mon, 13 Jun 2022 at 16:16, Jiangang Liu <
> > >  liujiangangp...@gmail.com 
> > >wrote:
> > >   
> > >Congratulations, Jingsong!
> > >   
> > >Best,
> > >Jiangang Liu
> > >   
> > >Martijn Visser  >  于2022年6月13日周一 16:06写道：
> > >   
> > >Like everyone has mentioned, this is very
> > well deserved.
> > >Congratulations!
> > >   
> > >Op ma 13 jun. 2022 om 09:57 schreef
> > Benchao Li <
> > >  libenc...@apache.org 
> > >   :
> > >   
> > >Congratulations, Jingsong! Well
> > deserved.
> > >   
> > >Rui Fan <1996fan...@gmail.com
> >  于2022年6月13日周一 15:53写道：
> > >   
> > >Congratulations, Jingsong!
> > >   
> > >Best,
> > >Rui Fan
> > >   
> > >On Mon, Jun 13, 2022 at 3:40 PM
> > LuNing Wang <
> > >  wang4lun...@gmail.com 
> > >   
> > >wrote:
> > >   
> > >Congratulations, Jingsong!
> > >   
> > >Best,
> > >LuNing Wang
> > >   
> > >Ingo Bürk <
> > airbla...@apache.org  于2022年6月13日周一
> > 15:36写道：
> > >   
> > >Congrats, Jingsong!
> > >   
> > >On 13.06.22 08:58, Becket
> > Qin wrote:
> > >Hi all,
> > >   
> > >I'm very happy to
> > announce that Jingsong Lee has joined the
> > >Flink
> > >PMC!
> > >   
> > >Jingsong became a
> > Flink committer in Feb 2020 and has been
> > >continuously
> > >contributing to the
> > project since then, mainly in Flink SQL.
> > >He
> > >has
> > >been
> > >quite active in the
> > mailing list, fixing bugs, helping
> > >verifying
> > >releases,
> > >reviewing patches and
> > FLIPs. Jingsong is also devoted to
> > >pushing
> > >Flink
> > >SQL
> > >to new use cases. He
> > spent a lot of time in implementing the
> > >Flink
> > >connectors for Apache
> > Iceberg. Jingsong is also the primary
> > >driver
> > >behind
> > >the effort of
> > flink-table-store, which aims to provide a
> > >stream-batch
> > >unified storage for
> > Flink dynamic tables.
> > >   
> > >Congratulations and
> > welcome, Jingsong!
> > >   
> > >Cheers,
> > >   
> > >Jiangjie (Becket) Qin
> > >(On behalf of the
> > Apache Flink PMC)
> > >   
> > >   
> > >   
> > >   
> > >   
> > >   
> > >--
> > >   
> > >Best,
> > >Benchao Li
> > >   
> > >   
> > >   
> > >   
> > >   
> > >   
> > >  
> > > 
> >
> >

[jira] [Created] (FLINK-28073) Table Store supports Flink 1.14

[Jingsong Lee (Jira)]

Jingsong Lee created FLINK-28073:


 Summary: Table Store supports Flink 1.14
 Key: FLINK-28073
 URL: https://issues.apache.org/jira/browse/FLINK-28073
 Project: Flink
  Issue Type: Improvement
  Components: Table Store
Reporter: Jingsong Lee
 Fix For: table-store-0.2.0






--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Created] (FLINK-28072) Set Hadoop FileSystem for Orc reader

[Jingsong Lee (Jira)]

Jingsong Lee created FLINK-28072:


 Summary: Set Hadoop FileSystem for Orc reader
 Key: FLINK-28072
 URL: https://issues.apache.org/jira/browse/FLINK-28072
 Project: Flink
  Issue Type: Improvement
  Components: Table Store
Reporter: Jingsong Lee
 Fix For: table-store-0.2.0


Now orc reader uses Hadoop FileSystem, but orc writer uses Flink FileSystem.

This can lead to some inconsistencies and possibly classloader loading issues.
We can unify this by setting the Hadoop FileSystem that we get from Flink for 
the orc reader.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee

[Yun Gao]

Congratulations, Jingsong!

Best,
Yun Gao


--
From:Jing Zhang 
Send Time:2022 Jun. 14 (Tue.) 11:05
To:dev 
Subject:Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee

Congratulations, Jingsong!

Best,
Jing Zhang

Leonard Xu  于2022年6月14日周二 10:54写道：

> Congratulations, Jingsong!
>
>
> Best,
> Leonard
>
> > 2022年6月13日 下午6:52，刘首维  写道：
> >
> > Congratulations and well deserved, Jingsong!
> >
> >
> > Best regards,
> > Shouwei
> > --原始邮件--
> > 发件人:
> "dev"
>;
> > 发送时间:2022年6月13日(星期一) 晚上6:09
> > 收件人:"dev"mailto:dev@flink.apache.org>;
> >
> > 主题:Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> >
> >
> >
> > Congratulations, Jingsong!
> >
> >
> > Best regards,
> > Yuxia
> >
> > - 原始邮件 -
> > 发件人: "Yun Tang"  > 收件人: "dev"  > 发送时间: 星期一, 2022年 6 月 13日 下午 6:12:24
> > 主题: Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> >
> > Congratulations, Jingsong! Well deserved.
> >
> > Best
> > Yun Tang
> > 
> > From: Xingbo Huang  > Sent: Monday, June 13, 2022 17:39
> > To: dev  > Subject: Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> >
> > Congratulations, Jingsong!
> >
> > Best,
> > Xingbo
> >
> > Jane Chan  >
> >  Congratulations, Jingsong!
> > 
> >  Best,
> >  Jane Chan
> > 
> >  On Mon, Jun 13, 2022 at 4:43 PM Shuo Cheng   wrote:
> > 
> >   Congratulations, Jingsong!
> >  
> >   On 6/13/22, Paul Lam  paullin3...@gmail.com> wrote:
> >Congrats, Jingsong! Well deserved!
> >   
> >Best,
> >Paul Lam
> >   
> >2022年6月13日 16:31，Lincoln Lee   写道：
> >   
> >Congratulations, Jingsong!
> >   
> >Best,
> >Lincoln Lee
> >   
> >   
> >Jark Wu mailto:imj...@gmail.com>
> 于2022年6月13日周一 16:29写道：
> >   
> >Congrats, Jingsong!
> >   
> >Cheers,
> >Jark
> >   
> >On Mon, 13 Jun 2022 at 16:16, Jiangang Liu <
> >  liujiangangp...@gmail.com 
> >wrote:
> >   
> >Congratulations, Jingsong!
> >   
> >Best,
> >Jiangang Liu
> >   
> >Martijn Visser   于2022年6月13日周一 16:06写道：
> >   
> >Like everyone has mentioned, this is very
> well deserved.
> >Congratulations!
> >   
> >Op ma 13 jun. 2022 om 09:57 schreef
> Benchao Li <
> >  libenc...@apache.org 
> >   :
> >   
> >Congratulations, Jingsong! Well
> deserved.
> >   
> >Rui Fan <1996fan...@gmail.com
>  于2022年6月13日周一 15:53写道：
> >   
> >Congratulations, Jingsong!
> >   
> >Best,
> >Rui Fan
> >   
> >On Mon, Jun 13, 2022 at 3:40 PM
> LuNing Wang <
> >  wang4lun...@gmail.com 
> >   
> >wrote:
> >   
> >Congratulations, Jingsong!
> >   
> >Best,
> >LuNing Wang
> >   
> >Ingo Bürk <
> airbla...@apache.org  于2022年6月13日周一
> 15:36写道：
> >   
> >Congrats, Jingsong!
> >   
> >On 13.06.22 08:58, Becket
> Qin wrote:
> >Hi all,
> >   
> >I'm very happy to
> announce that Jingsong Lee has joined the
> >Flink
> >PMC!
> >   
> >Jingsong became a
> Flink committer in Feb 2020 and has been
> >continuously
> >contributing to the
> project since then, mainly in Flink SQL.
> >He
> >has
> >been
> >quite active in the
> mailing list, fixing bugs, helping
> >verifying
> >releases,
> >reviewing patches and
> FLIPs. Jingsong is also devoted to
> >pushing
> >Flink
> >SQL
> >to new use cases. He
> spent a lot of time in implementing the
> >Flink
> >connectors for Apache
> Iceberg. Jingsong is also the primary
> >driver
> >behind
> >the effort of
> flink-table-store, which aims to provide a
> >stream-batch
> >unified storage for
> Flink dynamic tables.
> >   
> >Congratulations and
> welcome, Jingsong!
> >   
> >Cheers,
> >   
> >Jiangjie (Becket) Qin
> >(On behalf of the
> Apache Flink PMC)
> >   
> >   
> >   
> >   
> >   
> >   
> >--
> >   
> >Best,
> >Benchao Li
> >   
> >   
> >   
> >   
> >   
> >   
> >  
> > 
>
>