Re: [DISCUSS] Move flink-python to opt

Thanks for bringing up this DISCUSS Ufuk! Makes sense. +1 for doing this. Best, Jincheng Ufuk Celebi 于2019年2月25日周一 下午10:33写道： > Dear devs, > > what are your thoughts about moving flink-python (batch API) to opt > instead of having it in lib? The streaming counter part >

Re: [ANNOUNCE] Apache Flink 1.6.4 released

Thanks for being the release manager and the great job Jingcheng. > 在 2019年2月26日，下午12:12，Thomas Weise 写道： > > Jincheng, thanks for running the release! > > Please also send the announcement to user@ and annou...@apache.org (using > your @apache.org address) > > > On Mon, Feb 25, 2019 at 4:26

What component should take care of RunningJobRegistry?

Hi dev, While exploring FLINK RunningJobRegistry usage, I find it has three statuses and two components(Dispatcher and JobManagerRunner) have access to it. It is a bit wired and below shared my thoughts. 1. Three statuses(PENDING/RUNNING/DONE). The original version of RunningJobRegistry

Re: [ANNOUNCE] Apache Flink 1.6.4 released

Jincheng, thanks for running the release! Please also send the announcement to user@ and annou...@apache.org (using your @apache.org address) On Mon, Feb 25, 2019 at 4:26 AM Till Rohrmann wrote: > Thanks Jincheng for being our release manager. Great job! > > On Mon, Feb 25, 2019 at 10:48 AM

[jira] [Created] (FLINK-11749) Returns the stored leadership on ZooKeeperLeaderRetrievalService stated

TisonKun created FLINK-11749: Summary: Returns the stored leadership on ZooKeeperLeaderRetrievalService stated Key: FLINK-11749 URL: https://issues.apache.org/jira/browse/FLINK-11749 Project: Flink

[jira] [Created] (FLINK-11748) Optimize savepoint: Remove the task states and KeyedState into increments.

Mr.Nineteen created FLINK-11748: --- Summary: Optimize savepoint: Remove the task states and KeyedState into increments. Key: FLINK-11748 URL: https://issues.apache.org/jira/browse/FLINK-11748 Project:

Re: [DISCUSS] Move flink-python to opt

+1 Best, Vino Dawid Wysakowicz 于2019年2月26日周二 上午3:07写道： > Hi Ufuk, > > I think that makes absolute sense. +1 for this. > > Best, > > Dawid > > On 25/02/2019 18:46, Jeff Zhang wrote: > > +1 > > > > Ufuk Celebi 于2019年2月25日周一 下午10:33写道： > > > >> Dear devs, > >> > >> what are your thoughts about

Recommended module for connector ratelimiting?

Hi all, The PR that I've been iterating on w.r.t. Kafka ratelimiting — https://github.com/apache/flink/pull/7679 is now in a state where a lot of the rate limiting logic is generic and does not apply specifically to Kafka. I'd thus, like to move it to a module that is outside of the*

[jira] [Created] (FLINK-11747) Elasticsearch6 - Expose RestHighLevelClient to allow for custom sniffing

Samir Desai created FLINK-11747: --- Summary: Elasticsearch6 - Expose RestHighLevelClient to allow for custom sniffing Key: FLINK-11747 URL: https://issues.apache.org/jira/browse/FLINK-11747 Project:

Re: [DISCUSS] Move flink-python to opt

Hi Ufuk, I think that makes absolute sense. +1 for this. Best, Dawid On 25/02/2019 18:46, Jeff Zhang wrote: > +1 > > Ufuk Celebi 于2019年2月25日周一 下午10:33写道： > >> Dear devs, >> >> what are your thoughts about moving flink-python (batch API) to opt >> instead of having it in lib? The streaming

Re: to be contributer

Hi, I've added you to our JIRA! On Mon, Feb 25, 2019 at 5:26 PM kai wang wrote: > Hi, > > I want to contribute to Apache Flink. > Would you please give me the contributor permission? > My JIRA ID is frank wang >

[RESULT][VOTE] Clean up and reorganize the JIRA components

The proposal has been approved with +1 votes: - Timo - Robert - Jincheng - Shengjk1 - Chesnay - Till With +4 PMC votes, the vote has passed. Thanks everybody! I'll soon start with this effort! On Mon, Feb 25, 2019 at 1:28 PM Till Rohrmann wrote: > +1 > > On Mon, Feb 25, 2019 at 11:06 AM

[jira] [Created] (FLINK-11746) Add thrift format support in Flink

Yu Yang created FLINK-11746: --- Summary: Add thrift format support in Flink Key: FLINK-11746 URL: https://issues.apache.org/jira/browse/FLINK-11746 Project: Flink Issue Type: New Feature

Re: [DISCUSS] Move flink-python to opt

+1 Ufuk Celebi 于2019年2月25日周一 下午10:33写道： > Dear devs, > > what are your thoughts about moving flink-python (batch API) to opt > instead of having it in lib? The streaming counter part > (flink-streaming-python) is only as part of opt. > > I think we don't have many users of the Python batch API.

Re: Guidance to new Flink developers

Hi Feng, Regarding your particular contribution: I think you did a good job in gathering consensus on how the fix should be addressed. The PR's changes also matches the original discussions, with good test coverage and quality all in all. The only thing lacking was more attention from reviewers

to be contributer

Hi, I want to contribute to Apache Flink. Would you please give me the contributor permission? My JIRA ID is frank wang

Re: [DISCUSS] A more restrictive JIRA workflow

Hi, I think this is very valuable discussion and thank you for starting it. In general I am +1 for this proposal. I think though we must make it very clear that this will require a careful handling by committers. There are at least two cases that come to my mind that we need to be aware of: *

[DISCUSS] Move flink-python to opt

Dear devs, what are your thoughts about moving flink-python (batch API) to opt instead of having it in lib? The streaming counter part (flink-streaming-python) is only as part of opt. I think we don't have many users of the Python batch API. I think this will make the streaming/batch experience

Re: [DISCUSS] A more restrictive JIRA workflow

Really nice idea Timo, Thanks for taking the initiative to open this discussion. Although a side-effect, I consider it a big argument about my +1 the fact that now we create backpressure whenever needed at the JIRA level, rather than at the open PR level. The reason is that not accepting a PR

[jira] [Created] (FLINK-11745) [State TTL][E2E] Restore from the savepoint after the job cancelation

Andrey Zagrebin created FLINK-11745: --- Summary: [State TTL][E2E] Restore from the savepoint after the job cancelation Key: FLINK-11745 URL: https://issues.apache.org/jira/browse/FLINK-11745 Project:

[DISCUSS] A more restrictive JIRA workflow

Hi everyone, as some of you might have noticed during the last weeks, the Flink community grew quite a bit. A lot of people have applied for contributor permissions and started working on issues, which is great for the growth of Flink! However, we've also observed that managing JIRA and

Re: Guidance to new Flink developers

Hi Feng, Sorry to hear you feel that way. Our goal as a community is to make people as welcome as possible, but you must not forget we are only humans after all and we have limited capabilities ;) We always try to improve our processes, so if you have any suggestions what we could improve, feel

Re: [VOTE] Clean up and reorganize the JIRA components

+1 On Mon, Feb 25, 2019 at 11:06 AM Chesnay Schepler wrote: > +1 > > On 25.02.2019 09:51, Robert Metzger wrote: > > You are right. I've fixed it: > > > https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=103089605=7=6 > > > > On Thu, Feb 21, 2019 at 4:27 PM Chesnay

Re: [ANNOUNCE] Apache Flink 1.6.4 released

Thanks Jincheng for being our release manager. Great job! On Mon, Feb 25, 2019 at 10:48 AM Fabian Hueske wrote: > Thanks Jincheng for being the release manager! > > Am Mo., 25. Feb. 2019 um 09:49 Uhr schrieb Robert Metzger < > rmetz...@apache.org>: > > > Thank you Jincheng for running this

Guidance to new Flink developers

Hello guys, Sorry if this is already discussed question, is there some guidance in place to help new Flink developers to integrate to the community ? I’m new to the community and super happy after submitting my first pull request ( https://github.com/apache/flink/pull/7726 ) after some

Re: [ANNOUNCE] Flink 1.8 release branch has been cut

@Aljoscha Thanks for driving this and cutting the new branch. Looking forward to the release candidate :-) Best, Hequn On Mon, Feb 25, 2019 at 6:23 PM Kurt Young wrote: > Thanks Aljoscha! > > Best, > Kurt > > > On Mon, Feb 25, 2019 at 5:43 PM jincheng sun > wrote: > > > Thanks, Aljoscha! > >

[jira] [Created] (FLINK-11744) Provide stable/final toHexString for AbstractID

Stefan Richter created FLINK-11744: -- Summary: Provide stable/final toHexString for AbstractID Key: FLINK-11744 URL: https://issues.apache.org/jira/browse/FLINK-11744 Project: Flink Issue

Re: [DISCUSS] Improvement to Flink Window Operator with Slicing

Hi Rong, Thanks for the detailed summarization! It indeed involves lots of problems and unanswered questions which is i think not practical to solve in one shot. From my point of view, the performance issue with the sliding window is the root one and maybe most possible which user will run into.

Re: [ANNOUNCE] Flink 1.8 release branch has been cut

Thanks Aljoscha! Best, Kurt On Mon, Feb 25, 2019 at 5:43 PM jincheng sun wrote: > Thanks, Aljoscha! > That's very exciting, which means that the Flink community will have as a > big enhanced version coming soon! > > Cheers, > Jincheng > > Aljoscha Krettek 于2019年2月25日周一 下午5:27写道： > > > Hi

[jira] [Created] (FLINK-11743) Sticky E2E tests failed on travis

Chesnay Schepler created FLINK-11743: Summary: Sticky E2E tests failed on travis Key: FLINK-11743 URL: https://issues.apache.org/jira/browse/FLINK-11743 Project: Flink Issue Type: Bug

Re: [VOTE] Clean up and reorganize the JIRA components

+1 On 25.02.2019 09:51, Robert Metzger wrote: You are right. I've fixed it: https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=103089605=7=6 On Thu, Feb 21, 2019 at 4:27 PM Chesnay Schepler > wrote: Then the respective target components

Re: [ANNOUNCE] Apache Flink 1.6.4 released

Thanks Jincheng for being the release manager! Am Mo., 25. Feb. 2019 um 09:49 Uhr schrieb Robert Metzger < rmetz...@apache.org>: > Thank you Jincheng for running this release! > I've also tweeted about it from @ApacheFlink: > https://twitter.com/ApacheFlink/status/1099954183741022208 > > On Mon,

Re: [ANNOUNCE] Flink 1.8 release branch has been cut

Thanks, Aljoscha! That's very exciting, which means that the Flink community will have as a big enhanced version coming soon! Cheers, Jincheng Aljoscha Krettek 于2019年2月25日周一 下午5:27写道： > Hi Everyone, > > I just created the branch for the Flink 1.8 release [1] and updated the > version on master

[ANNOUNCE] Flink 1.8 release branch has been cut

Hi Everyone, I just created the branch for the Flink 1.8 release [1] and updated the version on master to 1.9-SNAPSHOT. Apparently we already had a 1.9.0 version in our jira [2]. I’ll create a first release candidate shortly, stay tuned! Best, Aljoscha [1]

[jira] [Created] (FLINK-11742) Push metrics t0 Pushgateway without "instance"

Tom Goong created FLINK-11742: - Summary: Push metrics t0 Pushgateway without "instance" Key: FLINK-11742 URL: https://issues.apache.org/jira/browse/FLINK-11742 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-11741) All implementations of deprecated TypeSerializer#ensureCompatibility method should be removed

Tzu-Li (Gordon) Tai created FLINK-11741: --- Summary: All implementations of deprecated TypeSerializer#ensureCompatibility method should be removed Key: FLINK-11741 URL:

[jira] [Created] (FLINK-11740) Ill-defined CompositeTypeSerializerSnapshot class signature

Tzu-Li (Gordon) Tai created FLINK-11740: --- Summary: Ill-defined CompositeTypeSerializerSnapshot class signature Key: FLINK-11740 URL: https://issues.apache.org/jira/browse/FLINK-11740 Project:

Re: [VOTE] Clean up and reorganize the JIRA components

You are right. I've fixed it: https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=103089605=7=6 On Thu, Feb 21, 2019 at 4:27 PM Chesnay Schepler wrote: > Then the respective target components should have a "split > Job-Submission" migration path attached to them. > None

Re: [ANNOUNCE] Apache Flink 1.6.4 released

Thank you Jincheng for running this release! I've also tweeted about it from @ApacheFlink: https://twitter.com/ApacheFlink/status/1099954183741022208 On Mon, Feb 25, 2019 at 4:04 AM Jark Wu wrote: > Thanks for being the release manager Jingcheng. > The 1.6.4 release contains a couple of