Re: [DISCUSS] Releasing Flink 1.8.3

Hi Jincheng, Thanks for kicking this discussion off! +1 to the 1.8.3 release as it would be nice to have these important fixes and also two months have passed since the last release. Besides, I wonder if I can be the release manager of 1.8.3 or work with you together @Jincheng? It's always excit

Re: [DISCUSS] Releasing Flink 1.8.3

wrote: > Thanks Hequn to be in change of the release ! > > Best, > Danny Chan > 在 2019年11月9日 +0800 PM3:59，Hequn Cheng ，写道： > > Hi Jincheng, > > > > Thanks for kicking this discussion off! > > > > +1 to the 1.8.3 release as it would be nice to have these impor

Re: [DISCUSS] Releasing Flink 1.8.3

Hi Chesnay, Jincheng Sure, I think it's good to have these fixes. Thanks a lot for providing the information about the security vulnerabilities! @Chesnay Best, Hequn On Thu, Nov 14, 2019 at 10:07 AM jincheng sun wrote: > +1 for try to eliminate the security vulnerabilities. Great thanks for >

Re: [DISCUSS] Expose or setup a secur...@flink.apache.org mailing list for security report and discussion

Hi Dian, Good idea! +1 to have a security mailing list. It is nice for Flink to have an official procedure to handle security problems, e.g., reporting, addressing and publishing. Best, Hequn On Thu, Nov 14, 2019 at 1:20 PM Jeff Zhang wrote: > Thanks Dian Fu for this proposal. +1 for creating

Re: [DISCUSS] Releasing Flink 1.8.3

gt; Alternatively, we could set this up as an opt-in upgrade, by adding a > separate profile that bumps the versions. This would present > users/providers who are concerned about the vulnerabilities an easy > workaround, at the risk of *some *things *maybe *not working. > > On 14/11/201

Re: [DISCUSS] Releasing Flink 1.8.3

ependencies in bugfix releases and b) it's a short-term change that we > >>> aren't allowing to mature properly. > >>> In contrast, the 1.10 release is significantly further away, hence no > >>> opt-in. > >>> > >>> He

Re: [DISCUSS] Releasing Flink 1.8.3

away. > > On 15/11/2019 13:44, Hequn Cheng wrote: > > Hi, > > > > @Chesnay Thanks a lot for the explanation. +1 to the opt-in approach for > > 1.8/1.9. > > @Ufuk Thank you for the nice summary. > > > > Looks good so far except that we need to postpo

Re: [DISCUSS] Release flink-shaded 9.0

Hi, Big +1 to release 9.0. It would be good if we can solve these security vulnerabilities. Thanks a lot for your nice work and kick off the release so quickly. On Fri, Nov 15, 2019 at 11:50 PM Ufuk Celebi wrote: > From what I can see, the Jackson version bump fixes quite a few > vulnerabilit

Re: [VOTE] FLIP-83: Flink End-to-end Performance Testing Framework

+1 (binding)! I think this would be very helpful to detect regression problems. Best, Hequn On Mon, Nov 18, 2019 at 4:28 PM vino yang wrote: > +1 (non-binding) > > Best, > Vino > > jincheng sun 于2019年11月18日周一 下午2:31写道： > > > +1 (binding) > > > > OpenInx 于2019年11月18日周一 下午12:09写道： > > > > > +1

Re: [DISCUSS] PyFlink User-Defined Function Resource Management

Thanks a lot for putting this together, Dian! Definitely +1 for this! It is great to make sure that the resources used by the Python process are managed properly by Flink’s resource management framework. Also, thanks to the guys that working on the unified memory management framework. Best, Hequn

Re: [VOTE] Release flink-shaded 9.0, release candidate #1

+1 (non-binding) * Test flink-shaded-jackson 9.0 against release-1.8 and release-1.9 (borrow the idea from @Ufuk) - 1.9 code: https://github.com/hequn8128/flink/commits/test_flink_shade_jackson_9.0_and_jackson_2.10.1_on_flink_1.9 - 1.9 travis: https://travis-ci.org/hequn8128/flink/builds/61586

Re: [DISCUSS] Releasing Flink 1.8.3

;> On Fri, Nov 15, 2019 at 2:27 PM Chesnay Schepler >> wrote: >> >> > I've kicked off a discussion about the next flink-shaded release, and >> > have opened PRs for adding the opt-in profile to 1.8/1.9. >> > >> > On 15/11/2019 13:54, Hequn Che

Re: [DISCUSS] Remove old WebUI

+1 to drop the old UI. On Sun, Nov 24, 2019 at 9:43 PM Jeff Zhang wrote: > +1 > > > Jark Wu 于2019年11月24日周日 下午8:46写道： > > > +1 to drop the old UI. > > > > On Fri, 22 Nov 2019 at 18:23, Flavio Pompermaier > > wrote: > > > > > +1 to drop the old UI > > > > > > On Thu, Nov 21, 2019 at 1:05 PM Ches

Re: [ANNOUNCE] Apache Flink-shaded 9.0 released

Thank you Chesnay for the great work! Also thanks a lot to the people who made this release possible! Best, Hequn On Mon, Nov 25, 2019 at 12:53 AM Chesnay Schepler wrote: > The Apache Flink community is very happy to announce the release of > Apache Flink-shaded 9.0. > > The flink-shaded projec

Re: [DISCUSS] Releasing Flink 1.8.3

> So just don't be blocked by it and feel free to cut the RC when other >> blocking issues are resolved. >> >> Thanks, >> Zhu Zhu >> >> Hequn Cheng 于2019年11月23日周六 下午9:08写道： >> >> > Hi Zhu Zhu, >> > >> > Thanks a lot for lettin

Re: [DISCUSS] Releasing Flink 1.8.3

, Nov 26, 2019 at 9:27 AM Hequn Cheng wrote: > Hi, > > @Ufuk Celebi Hi, we are very close now. There is one > issue(FLINK-13995 <https://issues.apache.org/jira/browse/FLINK-13995>) > left that I want to double-check with you guys. Once this is done, we can > create the

Re: [DISCUSS] Releasing Flink 1.8.3

ted here: > https://issues.apache.org/jira/projects/FLINK/versions/12346552 > > Best, > Jincheng > > Hequn Cheng 于2019年11月26日周二 下午8:18写道： > >> Hi all, >> >> I would like to share with you that all blockers are resolved now. If >> there are no more critical

[VOTE] Release 1.8.3, release candidate #1

Hi everyone, Please review and vote on the release candidate #1 for the version 1.8.3, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) The complete staging area is available for your review, which includes: * JIRA release notes [1], *

Re: [DISCUSS] Releasing Flink 1.8.3

Hi all, Thank you all for fixing issues of 1.8.3 release! The VOTE mail thread of the first RC of 1.8.3 has already been brought up. I would appreciate it if you can help to check the release and VOTE for the RC1. Thanks, Hequn On Wed, Nov 27, 2019 at 11:36 AM Hequn Cheng wrote: > Hi Jinch

Re: [VOTE] Release 1.8.3, release candidate #1

is not included in 1.8.3, but the fix version is > marked as fixed in 1.8.3 and so was included in the release note: >https://issues.apache.org/jira/browse/FLINK-10377 > > Regards, > Dian > > > 在 2019年11月28日，下午10:22，Hequn Cheng 写道： > > > > Hi everyone, >

Re: [VOTE] Release 1.8.3, release candidate #1

Hi all, The license problem has been resolved now. Thanks a lot for fixing the problem @Chesnay Schepler . I will create the RC2 and raise a new vote. The RC2 will be cut from the latest release-1.8 branch, i.e., it contains 4 more commits than RC1. Best, Hequn On Fri, Nov 29, 2019 at 11:45 PM

[VOTE] Release 1.8.3, release candidate #2

Hi everyone, Please review and vote on the release candidate #2 for the version 1.8.3, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) The complete staging area is available for your review, which includes: * JIRA release notes [1], *

Re: [VOTE] Release 1.8.3, release candidate #2

te and announcement PR > - Run examples of flink-example-table in IDE > > Best, > Jingsong Lee > > On Tue, Dec 3, 2019 at 10:29 AM Hequn Cheng wrote: > > > Hi everyone, > > > > Please review and vote on the release candidate #2 for the version 1.8.3, > >

Re: [VOTE] Release 1.8.3, release candidate #2

ed, Dec 4, 2019 at 11:54 AM Hequn Cheng wrote: > > > Hi everyone, > > > > Unfortunately, we need to cancel this vote due to a new critical issue( > > FLINK-15036 <https://issues.apache.org/jira/browse/FLINK-15036>) we have > > spotted recently. > > S

Re: [DISCUSS] Improve the Pyflink command line options (Adjustment to FLIP-78)

Hi all, Thanks a lot for the discussion! Using "#" also makes sense to me. And +1 to have these improvements in 1.10 as we don't want to introduce compatibility problems later. Looking forward to the vote! Best, Hequn On Thu, Dec 5, 2019 at 10:02 AM jincheng sun wrote: > Hi all, > > Thanks

Re: [VOTE] FLIP-88: PyFlink User-Defined Function Resource Management

+1 (binding) Best, Hequn On Thu, Dec 5, 2019 at 4:41 PM jincheng sun wrote: > +1（binding) > > Best, > Jincheng > > Jingsong Li 于2019年12月3日周二 下午7:30写道： > > > +1 (non-binding) > > > > Best, > > Jingsong Lee > > > > On Mon, Dec 2, 2019 at 5:30 PM Dian Fu wrote: > > > > > Hi Jingsong, > > > > > >

Re: [VOTE] Improve the Pyflink command line options (Adjustment to FLIP-78)

+1 (binding) Best, Hequn On Thu, Dec 5, 2019 at 5:43 PM jincheng sun wrote: > +1 (binding) > > Best, > Jincheng > > Dian Fu 于2019年12月5日周四 上午11:14写道： > > > +1 (non-binding) > > > > Regards, > > Dian > > > > > 在 2019年12月5日，上午11:11，Jark Wu 写道： > > > > > > +1 (binding) > > > > > > Best, > > > Jar

[VOTE] Release 1.8.3, release candidate #3

Hi everyone, Please review and vote on the release candidate #3 for the version 1.8.3, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) The complete staging area is available for your review, which includes: * JIRA release notes [1], *

Re: [ANNOUNCE] Feature freeze for Apache Flink 1.10.0 release

Hi Yu & Gary, Thanks a lot for your work and looking forward to the 1.10 release. :) Best, Hequn On Tue, Dec 10, 2019 at 1:29 AM Gary Yao wrote: > Hi all, > > We have just created the release-1.10 branch. Please remember to merge bug > fixes to both release-1.10 and master branches from now on

Re: [VOTE] Release 1.8.3, release candidate #3

e that 1000 > >> containers, good > >> > >> Danny Chan 于2019年12月10日周二 上午9:39写道： > >> > >>> Hi Hequn, > >>> > >>> +1 (non-binding) > >>> > >>> - verified checksums and hashes > >>> - built from l

[RESULT] [VOTE] Release 1.8.3, release candidate #3

Hi everyone, I'm happy to announce that we have unanimously approved this release. There are 10 approving votes, 3 of which are binding: * Jincheng (binding) * Ufuk (binding) * Till (binding) * Jingsong * Fabian * Danny * Yang Wang * Dian * Wei * Hequn There are no disapproving votes. Thanks ev

[ANNOUNCE] Apache Flink 1.8.3 released

Hi, The Apache Flink community is very happy to announce the release of Apache Flink 1.8.3, which is the third bugfix release for the Apache Flink 1.8 series. Apache Flink® is an open-source stream processing framework for distributed, high-performing, always-available, and accurate data streamin

Re: [RESULT] [VOTE] Release 1.8.3, release candidate #3

cker-flink/docker-flink/commit/4d85b71b7cf9fa4a38f8682ed13aa0f55445e32e > > [2] https://github.com/docker-library/official-images/ > > > > On Wed, Dec 11, 2019 at 3:30 AM Hequn Cheng > wrote: > > > > > Hi everyone, > > > > > > I'm hap

Re: [ANNOUNCE] Zhu Zhu becomes a Flink committer

Congrats, Zhu Zhu! Best, Hequn On Sun, Dec 15, 2019 at 6:11 AM Shuyi Chen wrote: > Congratulations! > > On Sat, Dec 14, 2019 at 7:59 AM Rong Rong wrote: > > > Congrats Zhu Zhu :-) > > > > -- > > Rong > > > > On Sat, Dec 14, 2019 at 4:47 AM tison wrote: > > > > > Congratulations!:) > > > > > >

Re: [ANNOUNCE] Weekly Community Update 2019/50

Hi Konstantin, Happy holidays and thanks a lot for your great job on the updates continuously. With the updates, it is easier for us to catch up with what's going on in the community, which I think is quite helpful. I'm wondering if I can do some help and cover this during your vocation. :) Best

Re: [ANNOUNCE] Weekly Community Update 2019/50

king forward to your updates! > > Cheers, > > Konstantin > > On Mon, Dec 16, 2019 at 5:53 AM Hequn Cheng wrote: > >> Hi Konstantin, >> >> Happy holidays and thanks a lot for your great job on the updates >> continuously. >> With the updates,

[DISCUSS] Releasing Flink 1.9.2

Hi everyone, It has already been two months since we released the Flink 1.9.1. We already have many important bug fixes from which our users can benefit in the release-1.9 branch (85 resolved issues). Therefore, I propose to create the next bug fix release for Flink 1.9. Most notable fixes are:

Re: [DISCUSS] Releasing Flink 1.9.2

st, > > Jincheng > > > > Best, > > Jincheng > > @sunjincheng121 <https://twitter.com/sunjincheng121> > > > > > > Hequn Cheng 于2019年12月18日周三 下午3:44写道： > > > > > Hi everyone, > > > > > > It has already been two months sin

Re: [DISCUSS] Releasing Flink 1.9.2

Christmas if there are no more blockers at that time. There is a chance that the 1.10 blocker resolution has calmed down a bit. Best, Hequn On Wed, Dec 18, 2019 at 7:05 PM Hequn Cheng wrote: > Hi Jincheng, > > Yes, your help would be very helpful. Thanks a lot! > > Best, Hequn > >

Re: [DISCUSS] Integrate Flink Docker image publication into Flink release process

Hi Patrick, Thanks a lot for your continued work on the Docker images. That’s really really a great job! And I have also benefited from it. Big +1 for integrating docker image publication into the Flink release process since we can leverage the Flink release process to make sure a more legitimacy

[ANNOUNCE] Weekly Community Update 2019/51

Dear community, Happy to share this week's brief community digest with updates on Flink 1.10 and Flink 1.9.2, a proposal to integrate Flink Docker image publication into Flink release process, a discussion on new features of PyFlink and a couple of blog posts. Enjoy. Flink Development ===

Re: [DISCUSS] FLIP-90: Support SQL 2016-2017 JSON functions in Flink SQL

equn On Mon, Dec 23, 2019 at 10:15 AM Jark Wu wrote: > Hi Forward, > > Thanks for creating the FLIP. +1 to start a vote. > > @Hequn Cheng @Kurt Young , > could you help to review the design doc too? > > Best, > Jark > > > On Mon, 23 Dec 2019 at 10:10,

Re: [DISCUSS] FLIP-90: Support SQL 2016-2017 JSON functions in Flink SQL

> > JSON_VALUE(v, 'lax $.b' ERROR ON ERROR) > == is equal to Table API ==> > v.jsonValue("lax $.b", JsonErrorStrategy.ERROR) > > Best, > Jark > > > On Thu, 26 Dec 2019 at 23:37, Hequn Cheng wrote: > >> Hi Jark & ForwardXu, >> >

[ANNOUNCE] Weekly Community Update 2019/52

Dear community, Happy to share a short community update this week. Due to the holiday, the dev@ mailing list is pretty quiet these days. Flink Development == * [sql] Jark proposes to correct the terminology of "Time-windowed Join" to "Interval Join" in Table API & SQL before 1.10 is

Re: [DISCUSS] FLIP-90: Support SQL 2016-2017 JSON functions in Flink SQL

; > > Thank you very much, Introducing new `TableSymbol`s sounds like a good > > idea. +1 for the proposal. > > > > I think this idea is good, I will add this in the documentation. > > > > > > Best, Forward > > > > Hequn Cheng 于2019年12月29日周日 下午3:41写道

[ANNOUNCE] Weekly Community Update 2020/01

Dear community, Happy new year! Wishing you a new year rich with the blessings of love, joy, warmth, and laughter. Wish Flink will get better and better. Nice to share this week’s community digest with an update on Flink-1.10.0, a proposal to set blink planner as the default planner for SQL Clien

Re: [DISCUSS] Set default planner for SQL Client to Blink planner in 1.10 release

+1 to make blink planner as the default planner for SQL Client, hence we can give the blink planner a bit more exposure. Best, Hequn On Fri, Jan 3, 2020 at 6:32 PM Jark Wu wrote: > Hi Benoît, > > Thanks for the reminder. I will look into the issue and hopefully we can > target it into 1.9.2 and

[DISCUSS] Include flink-ml-api and flink-ml-lib in opt

Hi everyone, FLIP-39[1] rebuilds Flink ML pipeline on top of TableAPI which moves Flink ML a step further. Base on it, users can develop their ML jobs and more and more machine learning platforms are providing ML services. However, the problem now is the jars of flink-ml-api and flink-ml-lib are

Re: [DISCUSS] Include flink-ml-api and flink-ml-lib in opt

his discussion Hequn! > > +1 for include `flink-ml-api` and `flink-ml-lib` in opt. > > BTW: I think would be great if bring up a discussion for upload multiple > Jars at the same time. as PyFlink JOB also can have the benefit if we do > that improvement. > > Best, > Jincheng > &

Re: [VOTE] FLIP-90: Support SQL 2016-2017 JSON functions in Flink SQL

+1 Thanks a lot for driving this. @ForwardXu Best, Hequn On Mon, Jan 13, 2020 at 10:07 AM Kurt Young wrote: > +1 > > Best, > Kurt > > > On Tue, Jan 7, 2020 at 2:59 PM Jingsong Li wrote: > > > +1 non-binding. Thanks Forward for driving this. > > > > Considering that it is made up of independent

Re: [ANNOUNCE] Dian Fu becomes a Flink committer

Congratulations, Dian. Well deserved! Best, Hequn On Thu, Jan 16, 2020 at 6:08 PM Leonard Xu wrote: > Congratulations! Dian Fu > > Best, > Leonard > > 在 2020年1月16日，18:00，Jeff Zhang 写道： > > Congrats Dian Fu ！ > > jincheng sun 于2020年1月16日周四 下午5:58写道： > >> Hi everyone, >> >> I'm very happy to a

Re: [DISCUSS] Releasing Flink 1.9.2

Best, Hequn On Wed, Dec 18, 2019 at 7:10 PM Hequn Cheng wrote: > Hi Till, > > I agree with your concerns and thanks a lot for your feedback! > > In fact, I also have those concerns. The reasons I started the DISCUSS are: > - Considering the low capacities, I want to start the discu

Re: [ANNOUNCE] Yu Li became a Flink committer

Congratulations Yu! Thanks a lot for being the release manager of the big 1.10 release. You are doing a very good job! Best, Hequn On Thu, Jan 23, 2020 at 6:29 PM Jingsong Li wrote: > Congratulations Yu, well deserved! > > And thanks for your great contribution to the 1.10 release. > > Best, >

Re: [DISCUSS] Releasing Flink 1.9.2

ase process! > > > > > > Cheers, > > > Till > > > > > > On Tue, Jan 21, 2020 at 11:02 PM jincheng sun < > sunjincheng...@gmail.com> > > > wrote: > > > > > > > Cool, looking forward the first RC of release 1.9.2. > &g

[VOTE] Release 1.9.2, release candidate #1

Hi everyone, Please review and vote on the release candidate #1 for the version 1.9.2, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) The complete staging area is available for your review, which includes: * JIRA release notes [1], *

Re: [VOTE] Release 1.9.2, release candidate #1

d a cluster and submitted examples via WebUI > - log files look good > > I also went over the release notes and updated a few things. > > On 24/01/2020 11:03, Hequn Cheng wrote: > > Hi everyone, > > > > Please review and vote on the release candidate #1 for the ve

Re: [VOTE] Integrate Flink Docker image publication into Flink release process

+1 Even though I prefer to contribute the Dockerfiles into the Flink main repo, but I think a dedicate repo is also a good idea. Thanks a lot for driving this! @Ufuk Celebi On Thu, Jan 30, 2020 at 12:02 PM Peter Huang wrote: > +1 (non-binding) > > > > On Wed, Jan 29, 2020 at 5:54 PM Yang Wang

Re: [VOTE] Release 1.9.2, release candidate #1

merge (minus release date to be > > updated once 1.9.2 is out) > > - No missing artifacts in staging area > > > > Thanks for managing the release Hequn! > > > > Cheers, > > Gordon > > > > On Wed, Jan 29, 2020 at 11:05 PM Hequn Cheng > wrote: &

Re: [VOTE] Release 1.9.2, release candidate #1

Hi everyone, Thanks a lot for your checking and voting for the release! I’ll summarize the result in another email. Thanks, Hequn On Thu, Jan 30, 2020 at 1:16 PM Hequn Cheng wrote: > +1 (non-binding) > > - check release note > - check signatures and hashes > - run e2e test on T

[RESULT] [VOTE] Release 1.9.2, release candidate #1

Hi everyone, I'm happy to announce that we have unanimously approved this release. There are 4 approving votes, 3 of which are binding: * Chesnay (binding) * Gordon (binding) * Jincheng (binding) * Hequn There are no disapproving votes. Thanks, everyone!

[ANNOUNCE] Apache Flink 1.9.2 released

Hi everyone, The Apache Flink community is very happy to announce the release of Apache Flink 1.9.2, which is the second bugfix release for the Apache Flink 1.9 series. Apache Flink® is an open-source stream processing framework for distributed, high-performing, always-available, and accurate dat

Re: [ANNOUNCE] Apache Flink 1.9.2 released

> > Best, > Jincheng > > Hequn Cheng 于2020年1月31日周五 下午6:55写道： > >> Hi everyone, >> >> The Apache Flink community is very happy to announce the release of >> Apache Flink 1.9.2, which is the second bugfix release for the Apache Flink >> 1.9 series. &

Re: [DISCUSS] Include flink-ml-api and flink-ml-lib in opt

Jan 8, 2020 at 9:15 PM Hequn Cheng wrote: > Hi Jincheng, > > Thanks a lot for your feedback! > Yes, I agree with you. There are cases that multi jars need to be > uploaded. I will prepare another discussion later. Maybe with a simple > design doc. > > Best, Hequn > > On W

Re: [DISCUSS] Include flink-ml-api and flink-ml-lib in opt

me simple ml tasks. > > Thanks, > > Jiangjie (Becket) Qin > > On Mon, Feb 3, 2020 at 4:34 PM jincheng sun > wrote: > >> Thank you for pushing forward @Hequn Cheng ! >> >> Hi @Becket Qin , Do you have any concerns on >> this ? >> >> Best,

Re: [DISCUSS] Upload the Flink Python API 1.9.x to PyPI for user convenience.

Hi Jincheng, +1 for this proposal. >From the perspective of users, I think it would nice to have PyFlink on PyPI which makes it much easier to install PyFlink. Best, Hequn On Tue, Feb 4, 2020 at 1:09 PM Jeff Zhang wrote: > +1 > > > Xingbo Huang 于2020年2月4日周二 下午1:07写道： > >> Hi Jincheng, >> >> T

Re: [DISCUSS] Include flink-ml-api and flink-ml-lib in opt

to offer the flink-ml libraries as > optional dependencies on the download page. Similar to how we offer the > different SQL formats and Hadoop releases [1]. > > [1] https://flink.apache.org/downloads.html > > Cheers, > Till > > On Mon, Feb 3, 2020 at 10:19 AM Hequn Ch

Re: [DISCUSS] Support User-Defined Table Function in PyFlink

Hi Xingbo, Thanks a lot for bringing up the discussion. Looks good from my side. One suggestion beyond the document: it would be nice to avoid Scala code in the flink-table module since we would like to get rid of Scala in the long-term[1][2]. Best, Hequn [1] https://cwiki.apache.org/confluence/

Re: [ANNOUNCE] Two new committers: Xingcan Cui and Nico Kruber

Congratulations! On Wed, May 9, 2018 at 4:40 AM, Rong Rong wrote: > Congratulations :-) > > On Tue, May 8, 2018 at 1:24 PM, Matthias J. Sax wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > Congrats! > > > > On 5/8/18 12:28 PM, Shuyi Chen wrote: > > > Congratulations! > >

Re: [TABLE][SQL] Unify UniqueKeyExtractor and DataStreamRetractionRules

Hi, thanks for bringing up this discussion. I agree to unify the UniqueKeyExtractor and DataStreamRetractionRules, however I am not sure if it is a good idea to implement it with RelShuttle. Theoretically, retraction rules and other rules may depend on each other. So, by using a RelShuttle instead

Re: [TABLE][SQL] Unify UniqueKeyExtractor and DataStreamRetractionRules

ction traits > with respect of parent/children). > > I was thinking about the last approach - rules executed after adding > traits should preserve consistency of those traits. That’s why I didn’t > mind setting up retractions rules in a shuttle. > > Piotrek > > > On

Re: [TABLE][SQL] Unify UniqueKeyExtractor and DataStreamRetractionRules

misation rules that on their own DO > brake those traits and converting them into rules that DO NOT brake them. > We could use such visitor/shuttle as a validation step or a clean up step > after a rewrite. > > Piotrek > > On 16 Jun 2018, at 10:42, Hequn Cheng wrote: > > Hi Piotr :-

Re: Facing issue in RichSinkFunction

Hi Amol, The implementation of the RichSinkFunction probably contains a field that is not serializable. To avoid serializable exception, you can: 1. Marking the field as transient. This makes the serialization mechanism skip the field. 2. If the field is part of the object's persistent state, the

Re: Confusions About JDBCOutputFormat

Hi wangsan, I agree with you. It would be kind of you to open a jira to check the problem. For the first problem, I think we need to establish connection each time execute batch write. And, it is better to get the connection from a connection pool. For the second problem, to avoid multithread pro

Re: Confusions About JDBCOutputFormat

connection is closed? > > May be we could use a Timer to test the connection periodically and keep > it alive. What do you think? > > I will open a jira and try to work on that issue. > > Best, > wangsan > > > > On Jul 10, 2018, at 8:38 PM, Hequn Cheng wrote: >

Re: Confusions About JDBCOutputFormat

> connection pools. Test and refresh the connection periodically can simply > solve this problem. I’ve implemented this at https://github.com/apache/ > flink/pull/6301, It would be kind of you to review this. > > Best, > wangsan > > > > On Jul 11, 2018, at 2:25 PM, Hequ

Re: [ANNOUNCE] Apache Flink 1.5.1 released

Cool, thanks to Chesnay! Best, Hequn On Fri, Jul 13, 2018 at 8:25 PM, vino yang wrote: > Thanks Chesnay, great job! > > Thanks, > Vino > > 2018-07-13 20:20 GMT+08:00 Till Rohrmann : > >> Great to hear. Big thank you to the community for the hard work and to >> Chesnay for being our release mana

[DISCUSS][TABLE] How to handle empty delete for UpsertSource

Hi all, Currently, I am working on FLINK-8577 Implement proctime DataStream to Table upsert conversion . And a design doc can be found here . It recei

Re: [DISCUSS][TABLE] How to handle empty delete for UpsertSource

query at all. Not only for the UpsertSource -> Calc -> > UpsertSink, but also for example in the future for joins or ORDER BY > (especially with LIMIT) as well. > > > > I would apply same reasoning to FLINK-9528. > > > > Piotrek > > > >>

Re: [Proposal] Utilities for reading, transforming and creating Streaming savepoints

Hi Gyula, +1 for this feature. State bootstrapping and state analytics will be very helpful. On Thu, Aug 23, 2018 at 4:09 AM Gyula Fóra wrote: > Hi Shuyi, > > The tool allows you to convert a Flink DataSet containing the individual > state rows, (key, state) pairs, into a state for a streaming

Re: [DISCUSS][TABLE] How to handle empty delete for UpsertSource

eletes or not).* I think the result is clear if we clearly define that the upsert source ignore empty deletes. Flink only skip or ingest messages according to the sql/table-api provided by users. Thanks, Hequn On Thu, Aug 23, 2018 at 6:04 PM Piotr Nowojski wrote: > Hi, > > Thanks for ver

Re: [DISCUSS] Remove the slides under "Community & Project Info"

Hi Stephan, Thanks for bringing up this discussion. I think we can just remove it, because slides have already be provided from the `Flink Forward` section in this page. Adding another slides section not only brings redundancy but also introduces problems you listed above. Best, Hequn On Sun, Au

Re: [DISCUSS][TABLE] How to handle empty delete for UpsertSource

d > handle messages as follows: > - upsert message/flag=true: upsert messages are handled as regular > message. If the predicate evaluates to false, all but the key fields are > set to null and the message is forwarded as a delete message > - delete message/flag=false: delete messages are c

Re: [ANNOUNCE] New committer Gary Yao

Congratulations Gary! Hequn On Fri, Sep 7, 2018 at 11:16 PM Matthias J. Sax wrote: > Congrats! > > On 09/07/2018 08:15 AM, Timo Walther wrote: > > Congratulations, Gary! > > > > Timo > > > > > > Am 07.09.18 um 16:46 schrieb Ufuk Celebi: > >> Great addition to the committers. Congrats, Gary! > >

Re: [DISCUSS] Dropping flink-storm?

Hi, +1 to drop it. It seems that few people use it. Best, Hequn On Fri, Sep 28, 2018 at 10:22 PM Chesnay Schepler wrote: > I'm very much in favor of dropping it. > > Flink has been continually growing in terms of features, and IMO we've > reached the point where we should cull some of the more

Re: [DISCUSS] Improvements to the Unified SQL Connector API

Hi, Thanks a lot for the proposal. I like the idea to unify table definitions. I think we can drop the table type since the type can be derived from the sql, i.e, a table be inserted can only be a sink table. I left some minor suggestions in the document, mainly include: - Maybe we also need to a

Re: [DISCUSS] Improvements to the Unified SQL Connector API

> supposed to be written only by some producer. What do you guys think? > > Shuyi > > On Thu, Oct 4, 2018 at 7:31 AM Hequn Cheng wrote: > > > Hi, > > > > Thanks a lot for the proposal. I like the idea to unify table > definitions. > > I think we can drop

Re: [DISCUSS] [Contributing] (2) - Review Steps

+1 On Tue, Oct 9, 2018 at 3:25 PM Till Rohrmann wrote: > +1 > > On Tue, Oct 9, 2018 at 9:08 AM Zhijiang(wangzhijiang999) > wrote: > > > +1 > > -- > > 发件人：vino yang > > 发送时间：2018年10月9日(星期二) 14:08 > > 收件人：dev > > 主 题：Re: [DISCUSS]

Re: Creating a slide set for a Flink intro talk

Hi @Fabian Thanks a lot for creating the slide. It is great to have an introduction slide to our users. I have taken a look at the slide. The content of the slide is good and I only left some minor suggestions. Best, Hequn On Sat, Oct 13, 2018 at 10:12 AM jincheng sun wrote: > @Fabian Hueske

Re: [DISCUSS] [Contributing] (3) - Review Tooling

Hi, I'm slightly prefer the bot option. The bot can post the review template automatically. But I do agree that we can start with a low-tech solution and add a bot later if find it helpful. Best, Hequn On Wed, Oct 17, 2018 at 11:17 AM Jin Sun wrote: > +1 > > On Tue, Oct 16, 2018 at 7:51 PM Tzu

Re: [DISCUSS] Enhancing the functionality and productivity of Table API

Hi Jincheng, Thanks a lot for your proposal. It is very encouraging! As we all know, SQL is a widely used language. It follows standards, is a descriptive language, and is easy to use. A powerful feature of SQL is that it supports optimization. Users only need to care about the logic of the progr

Re: [DISCUSS] Table API Enhancement Outline

Hi, Thank you all for the great proposal and discussion! I also prefer to move on to the next step, so +1 for opening the JIRAs to start the work. We can have more detailed discussion there. Btw, we can start with JIRAs which we have agreed on. Best, Hequn On Tue, Nov 20, 2018 at 11:38 PM Shaoxu

Re: [VOTE] Release 1.7.0, release candidate #2

Hi, I'm trying to check if the source release is building properly. And found that NonHAQueryableStateFsBackendITCase failed when run `mvn install`. This should not be a release blocker, however, I ceated a pr[1] to make it more stable. Best, Hequn [1] https://issues.apache.org/jira/browse/FLINK

Re: [DISCUSS] Long-term goal of making flink-table Scala-free

Hi Timo, Thanks for the effort and writing up this document. I like the idea to make flink-table scala free, so +1 for the proposal! It's good to make Java the first-class citizen. For a long time, we have neglected java so that many features in Table are missed in Java Test cases, such as this o

Re: [ANNOUNCE] Apache Flink 1.7.0 released

A great release, Thanks a lot for the great work Till! And also thanks to the whole Flink community! Let's moving forward. Best, Hequn On Sat, Dec 1, 2018 at 12:31 AM Tzu-Li Chen wrote: > Thanks a lot for being the release manager Till! And > thanks for the great work Flink community! > > Best

Re: [DISCUSS] Releasing Flink 1.6.3

Hi Gordon, Thanks for the discussion! +1 for creating the 1.6.3 release. It would be nice if we have a new fix for the previous release. Best, Hequn On Wed, Dec 12, 2018 at 11:05 PM Till Rohrmann wrote: > Thanks for starting this discussion Gordon. +1 for creating the 1.6.3 > release since we

Re: [DISCUSS] Releasing Flink 1.7.1

Hi Chesnay, Thanks for the efforts. +1 for the release. It's nice to have these fixes. Best, Hequn On Wed, Dec 12, 2018 at 11:09 PM Till Rohrmann wrote: > Thanks for starting this discussion Chesnay. +1 for creating the 1.7.1 > release since it already contains very useful fixes. > > Cheers, >

Re: [VOTE] Release 1.7.1, release candidate #2

Hi Chesnay, Thanks for the vote and great job! I checked the release notes and found the following errors: - Missing bugs: [FLINK-10874] Kafka 2.0 connector testMigrateFromAtLeastOnceToExactlyOnce failure [FLINK-10987] LICENSE and NOTICE files are not correct - Improvement should be removed: [FLI

Re: Flink 1.7 doesn't work with Kafka Table Source Descriptors

Hi dhanuka, I failed to reproduce your error with release-1.7.0. It seems Kafka.toConnectorProperties() should be called instead of ConnectorDescriptor.toConnectorProperties(), the latter one is an abstract class, which lead to the AbstractMethodError. >From the picture uploaded, it is strange th

Re: Flink 1.7 doesn't work with Kafka Table Source Descriptors

> org.apache.flink.table.descriptors.ConnectTableDescriptor.registerTableSource(ConnectTableDescriptor.scala:46) > at > org.monitoring.stream.analytics.FlinkTableSourceLatest.main(FlinkTableSourceLatest.java:97) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMeth

Re: Multiple select single result

Hi dhanuka, > I am trying to deploy 200 SQL unions and it seems all the tasks getting failing after some time. Would be great if you can show us some information(say exception stack) about the failure. Is it caused by OOM of job manager? > How do i allocate memory for task manager and job manager

<    1   2   3   4   >