Re: [VOTE] Release Apache Flink 1.6.4, release candidate #1

+1 (binding) - "mvn clean verify" ran successfully (I ran into an issue with the ES5 connector on Google Cloud, but that's only a test instability that existed already in 1.6.2) https://issues.apache.org/jira/browse/FLINK-11720 - checked staging repo contents, validated a signature there - Ran

[jira] [Created] (FLINK-11720) ES5: ElasticsearchSinkITCase failing

Robert Metzger created FLINK-11720: -- Summary: ES5: ElasticsearchSinkITCase failing Key: FLINK-11720 URL: https://issues.apache.org/jira/browse/FLINK-11720 Project: Flink Issue Type: Task

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

point is the important one, whereas the rest are probably just > things that slipped through while updating the proposal. > > On 20.02.2019 11:04, Timo Walther wrote: > +1 > > Thanks for the proposal. > > Timo > > Am 20.02.19 um 10:53 schrieb Robert Metzger: > Hey

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

+1 Thanks Timo! On Wed, Feb 20, 2019 at 11:04 AM Timo Walther wrote: > +1 > > Thanks for the proposal. > > Timo > > Am 20.02.19 um 10:53 schrieb Robert Metzger: > > Hey all, > > > > As discussed in the last days, I'm proposing to clean up and reorgan

[VOTE] Clean up and reorganize the JIRA components

Hey all, As discussed in the last days, I'm proposing to clean up and reorganize our JIRA tickets. Chesnay proposed to approve the final proposal through a VOTE. Here is the proposal: https://cwiki.apache.org/confluence/display/FLINK/Proposal+for+new+JIRA+Components Please vote with: [ ] +1

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

m 20.02.19 um 10:09 schrieb Chesnay Schepler: > > I would prefer if you'd start a vote with a new cleaned up proposal. > > > > On 18.02.2019 15:23, Robert Metzger wrote: > >> I added "Runtime / Configuration" to the proposal: > >> > https://cwiki.apach

Re: [DISCUSS] Improve the flinkbot

. The only thing that has a nice range of colors are hearts, but I think that's not a good fit in our case :) On Fri, Feb 15, 2019 at 12:59 PM Chesnay Schepler wrote: > The bot could check that the PR title to starts with [FLINK-X] or [hotfix]. > > On 13.02.2019 10:29, Robert Metz

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

t 10:51 AM Chesnay Schepler wrote: > The only parent I can think of is "Infrastructure", but I don't quite > like it :/ > > +1 for "Runtime / Configuration"; this is too general to be placed in > coordination imo. > > On 12.02.2019 18:25, Robert Metzge

Re: Problems with local build

s a last > > commit in master branch. > > > > чт, 14 февр. 2019 г. в 13:32, Robert Metzger : > > > >> Hey Aleksandr, > >> > >> let's first try to resolve issue 1. > >> > >> Which maven version are you using? > >> What's the commit sha you are trying to build? > >> > > >

Re: [DISCUSS] Start a user...@flink.apache.org mailing list for the Chinese-speaking community?

Gordon > > On Wed, Feb 13, 2019 at 5:05 PM Robert Metzger > wrote: > > > Hey all, > > > > I'm now getting more and more MODERATE emails from the mailing list > service > > for the user-zh@ list from people trying to subscribe. > > I would like to a

Re: Applying for flink contributor permission

Hey, I gave you contributor permissions. Thanks a lot for helping with the translation effort! On Mon, Feb 18, 2019 at 7:13 AM 陈利飞 wrote: > My jira account is: hustclf > > 陈利飞 于2019年2月18日周一 下午2:08写道： > > > Hi, all: > > I am applying for flink contributor permission, I want to help to > >

Re: [ANNOUNCE] Apache Flink 1.7.2 released

Thank you Gordon! Help spread the word here: https://twitter.com/ApacheFlink/status/1097416946688102401 On Mon, Feb 18, 2019 at 7:41 AM Dian Fu wrote: > Great job. It's great to have a more stable 1.7 release available. Thanks > @Gordon for making it happen. > > Regards, > Dian > > 在

Re: [DISCUSS] Releasing Flink 1.8 / Feature Freeze

I'm not involved enough with the development to say whether end of this week is a realistic deadline. But I see that it makes sense to release 1.8 soon, if it is blocking the Table API refactoring. There are 5 blockers assigned to the 1.8.0 release:

[jira] [Created] (FLINK-11642) Add S3 config key "fs.s3a.endpoint" for custom S3 regions

Robert Metzger created FLINK-11642: -- Summary: Add S3 config key "fs.s3a.endpoint" for custom S3 regions Key: FLINK-11642 URL: https://issues.apache.org/jira/browse/FLINK-11642 Proj

Re: Would you please give me the permission as a contributor?

> Fei Han > > > ---------- > 发件人：Robert Metzger > 发送时间：2019年2月15日(星期五) 19:17 > 收件人：dev ; hanfeizi0409 > 主 题：Re: Would you please give me the permission as a contributor? > > Hey, > > I just granted you the permissions. > > I'm curious to learn in which part of Flin

Re: [VOTE] Release Apache Flink 1.7.2, release candidate #1

+1 - started flink on yarn on google cloud dataproc (hadoop 2.9.2) - the files in the staging repo look correct (right version in the pom.xml, also for the quickstarts) On Fri, Feb 15, 2019 at 1:05 PM Averell wrote: > +1 > > * Compiled from source > * Downloaded jars from repository > *

Re: Would you please give me the permission as a contributor?

Hey, I just granted you the permissions. I'm curious to learn in which part of Flink you'd like to contribute. Best regards, Robert On Fri, Feb 15, 2019 at 9:33 AM hanfeizi0409 wrote: > Hi Guys, > > I want to contribute to Apache Flink. > Would you please give me the permission as a

Re: Problems with local build

Hey Aleksandr, let's first try to resolve issue 1. Which maven version are you using? What's the commit sha you are trying to build?

Re: request for access

Hey, I added you to our JIRA. On Wed, Feb 13, 2019 at 9:07 AM 刘建刚 wrote: > Hi Guys, > > I want to contribute to Apache Flink. > Would you please give me the permission as a contributor? > My JIRA Username is Jiangang. My JIRA full name is Liu. >

Re: Request for contribution access

Hi, I added you to our JIRA. On Wed, Feb 13, 2019 at 9:17 AM Xin Ma wrote: > Hi Guys, > > I want to contribute to Apache Flink. > Would you please give me the permission as a contributor? > My JIRA ID is iluvex. > > > Best regards, > > Xin >

Re: Request for contribution access

Hey, I added you to our JIRA On Wed, Feb 13, 2019 at 9:17 AM 区 <670694...@qq.com> wrote: > Hi Guys, > > > I want to contribute to Apache Flink. > Would you please give me the permission as a contributor? > My JIRA Username is ysqwhiletrue. My JIRA full name sishu.yss.

Re: flink

Hi, I added you! On Wed, Feb 13, 2019 at 10:01 AM Asura <1402357...@qq.com> wrote: > Hi Guys, > > I want to contribute to Apache Flink. > Would you please give me the permission as a contributor? > My JIRA ID is Gongwenzhou.

Re: Apply JIRA contributor

Hi, I added you! On Wed, Feb 13, 2019 at 2:19 PM Yaoting Gong wrote: > Hi Guys, > > I want to contribute to Apache Flink. > Would you please give me the permission as a contributor? > My JIRA ID is Tom Goong > > Thanks. > Tom Goong >

Re: [DISCUSS] Releasing Flink 1.6.4

Can we start creating the release candidate for the 1.6.4 version, or are there still commits in the "release-1.6" branch missing? On Wed, Feb 13, 2019 at 9:41 AM jing wrote: > +1 > > > > -- > Sent from: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/ >

Re: [DISCUSS] Improve the flinkbot

. If nobody objects here, I will activate this new feature in the coming days. On Wed, Feb 13, 2019 at 10:29 AM Robert Metzger wrote: > Hey all, > > the flinkbot has been active for a week now, and I hope the initial > hiccups have been resolved :) > > I wanted to start this as

[DISCUSS] Improve the flinkbot

Hey all, the flinkbot has been active for a week now, and I hope the initial hiccups have been resolved :) I wanted to start this as a permanent thread to discuss problems and improvements with the bot. *So please post here if you have questions, problems or ideas how to improve it!*

Re: [DISCUSS] Start a user...@flink.apache.org mailing list for the Chinese-speaking community?

criber to the list is accidentally posting from a different address). Which Flink committer is willing to help out here? Best, Robert On Tue, Jan 29, 2019 at 10:29 AM Jark Wu wrote: > Cheers! > > Subscribed. Looking forward to the first Chinese question ;) > > On Tue, 29 Jan

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

", and remove the major "Tests" > category. > > re core/config: As an example, where (under Runtime) would you place the > introduction of the ConfigOption class? > > On 11.02.2019 11:31, Robert Metzger wrote: > > Thanks a lot for your feedback! >

Re: [ANNOUNCE] New Flink PMC member Thomas Weise

Congrats Thomas! I'm very happy to have you in our PMC as an experienced open source advocate :) On Tue, Feb 12, 2019 at 11:09 AM jincheng sun wrote: > Congrats Thomas ! > > Cheers, > Jincheng > > Fabian Hueske 于2019年2月12日周二 下午5:59写道： > >> Hi everyone, >> >> On behalf of the Flink PMC I am

Re: [DISCUSS] Releasing Flink 1.7.2

Cool! Then let's do the release together. I haven't done it in a while, but we'll manage. Could you start a separate [DISCUSS] thread for the 1.6.4 release? On Mon, Feb 11, 2019 at 1:39 PM jincheng sun wrote: > Thank you for agreeing to release Flink 1.6.4. @Robert Metzger > @Till Ro

Re: [DISCUSS] Releasing Flink 1.7.2

+1 on a 1.6.4 release. Jincheng, if you want to be the release manager, I'm happy to assist you with my PMC powers :) On Mon, Feb 11, 2019 at 1:24 PM Till Rohrmann wrote: > Hi Jincheng, > > releasing a new bug fix release for the 1.6.x series is a really good idea > since it already contains a

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

IPs, presentations, > > and documentation. > > - Rename "SQL/Query Planner" to "SQL/Planner" a query is read-only > > operation but we support things like INSERT INTO etc.. Planner is more > > generic. > > - Rename "Gelly" to "Graph Pro

Re: Apply for Flink contributor permission for JIRA

Hey, I added you to our JIRA. On Mon, Feb 11, 2019 at 8:16 AM shengjk1 wrote: > Hi Guys, > > Could anyone give me the contributor permission ? > > > My Jira ID is shengjk1 > > > > > thanks > >

[DISCUSS] Clean up and reorganize the JIRA components

Hi all, I am currently trying to improve how the Flink community is handling incoming pull requests and JIRA tickets. I've looked at how other big communities are handling such a high number of contributions, and I found that many are using GitHub labels extensively. An integral part of the

Re: Flink release schedule

Hey Ufuk, I agree! We should have regular discussions here on the list for scoping releases, and then put this to the website. The Beam project has a pretty nice roadmap [1] available on their site. I actually don't really know if there's an agreed upon release schedule in the Flink community

Re: Please add me for Flink contribution

shek}} > > On Sat, Feb 2, 2019 at 3:30 AM Robert Metzger wrote: > >> Hey Abhishek, >> I granted you contributor permission in our JIRA! >> >> May I ask what you are planning to work on? >> >> Best, >> Robert >> >> On Sat, Feb 2, 2019 at 2:

Re: [DISCUSS] Contributing Chinese website and docs to Apache Flink

e for flink-web, here > is the branch: https://github.com/wuchong/flink-web/tree/multi-language > > @Fabian Hueske +1 to start contribute flink-web > first. > > @Gordon That's a good idea to add the document checklist to the review > process. I have included this in the pro

Re: Please add me for Flink contribution

Hey Abhishek, I granted you contributor permission in our JIRA! May I ask what you are planning to work on? Best, Robert On Sat, Feb 2, 2019 at 2:56 AM abhishek sharma wrote: > Please provide me the contribution permission. > > email: abhion...@yahoo.com > apache-username: abhioncbr > >

Re: Request contributor permission

d you also help me with the FLIP permissions? > > Thanks, > > Jiangjie (Becket) Qin > > On Thu, Jan 31, 2019 at 5:56 PM Robert Metzger > wrote: > > > Hey Becket, > > > > I gave you contributor permissions in our JIRA. (Assuming your JIRA id is > > "bec

Re: [DISCUSS] Start new Review Process

t; >>>>> > >>>>> Since there is another lively discussion going on about a bot for > >>>>> stale PRs, I'm wondering what the future plans for @flinkbot are. Do > >>>>> we want to have multiple bots for the project? Or do you pl

Re: [DISCUSS] Standard / Convention for common connector metrics

Hey Becket, thanks a lot for your proposal! Do you have an overview over the current situation of the metrics in the connectors? Which connectors expose metrics at all? Are they different? On Thu, Jan 31, 2019 at 8:44 AM Becket Qin wrote: > Hi folks, > > I was trying to add some metrics to

Re: Request contributor permission

Hey Becket, I gave you contributor permissions in our JIRA. (Assuming your JIRA id is "becket_qin"). On Thu, Jan 31, 2019 at 10:37 AM Becket Qin wrote: > Hi, > > Could someone help me with getting the contributor's permission so I can > create FLIPs and assign JIRA tickets? > > Thanks, > >

Re: [DISCUSS] Start new Review Process

t; > > > @flinkbot approve contribution > > > > > @flinkbot approve consensus > > > > > > > > 2) Extend the last line of the description by adding something like > "See > > > > Pull Request Review Guide for how to use the Flink bot."? &

Re: [DISCUSS] Start a user...@flink.apache.org mailing list for the Chinese-speaking community?

Flink community size and increase > > interaction between the English and non-English speaking community. > > :-) > > > > On Mon, Jan 28, 2019 at 6:02 PM jincheng sun > > wrote: > > > > > > +1，I like the idea very much！ > > > > > > Rober

Re: [DISCUSS] Start a user...@flink.apache.org mailing list for the Chinese-speaking community?

> wrote: > > > +1. Looking forward to it. > > > > On Thu, Jan 24, 2019 at 7:41 PM Robert Metzger > > wrote: > > > > > Thanks for your response. > > > > > > You are right, I'm proposing "user...@flink.apache.org" as the mailing &

Re: [DISCUSS] Start a user...@flink.apache.org mailing list for the Chinese-speaking community?

stions / discussions / replies from developers can be indexed > and searchable. > Moreover, it'll give the community more insight in how active a > Chinese-speaking contributor is helping with user requests, > which in general is a form of contribution that the community always merits > a lot. >

[DISCUSS] Start a user...@flink.apache.org mailing list for the Chinese-speaking community?

Hey all, I would like to create a new user support mailing list called " user...@flink.apache.org" to cater the Chinese-speaking Flink community. Why? In the last year 24% of the traffic on flink.apache.org came from the US, 22% from China. In the last three months, China is at 30%, the US at

[jira] [Created] (FLINK-11418) Unable to build docs in Docker image

Robert Metzger created FLINK-11418: -- Summary: Unable to build docs in Docker image Key: FLINK-11418 URL: https://issues.apache.org/jira/browse/FLINK-11418 Project: Flink Issue Type: Bug

Re: [DISCUSS] Start new Review Process

I have the bot now running in https://github.com/flinkbot/test-repo/pulls Feel free to play with it. On Wed, Jan 23, 2019 at 10:25 AM Robert Metzger wrote: > Okay, cool! I'll let you know when the bot is ready in a test repo. > While you (and others) are testing it, I'll open a PR for th

Re: [DISCUSS] Start new Review Process

y. > I think it would be good to extend the PR Review guide [1] with a section > about the bot and how to use it. > > Fabian > > [1] https://flink.apache.org/reviewing-prs.html > > Am Mi., 23. Jan. 2019 um 10:03 Uhr schrieb Robert Metzger < > rmetz...@apache.org>

Re: Applying for Flink contributor permission

Hey Lavkesh, welcome to the Flink community! I've added you as a contributor to our JIRA! Happy coding :) On Wed, Jan 23, 2019 at 9:32 AM Lavkesh Lahngir wrote: > Please provide me controbution permission. > email: lavkes...@gmail.com > apache-username: lavkesh > > Thank you >

Re: Applying for Flink contributor permission

Hey Matthieu, welcome to the Flink community! I've added you as a contributor to our JIRA! Happy coding :) On Wed, Jan 23, 2019 at 9:39 AM Matthieu Bonneviot < matthieu.bonnev...@datadome.co> wrote: > Hi > > Please provide me contribution permission. > email: matthieu.bonnev...@datadome.co >

Re: [DISCUSS] Start new Review Process

Hey, as I've mentioned already in the pull request, I have started implementing a little bot for GitHub that tracks the checklist [1] The bot is monitoring incoming pull requests. It creates a comment with the checklist. Reviewers can write a message to the bot (such as "@flinkbot approve

Re: [DISCUSS] Change underlying Frontend Architecture for Flink Web Dashboard

Hey Fabian, First of all, big +1 on the effort! Two quick thoughts: - I would suggest to build a new UI outside of the main Flink project, and look at replacing the current one, once a new one has reached feature parity. - I would also suggest to go with React, as it seems the leading frontend

Re: [DISCUSS] Flink Cluster Overview Dashboard Improvement Proposal

ng with this here at work as well, so implementing at least a >first MVP might be feasible as well, before getting to deep into A1 >specifics. But that basically means that you guys are open to change the >underlying web/JS technology, yeah? > > Cheers > > -- >

Re: [DISCUSS] Flink Cluster Overview Dashboard Improvement Proposal

Hey Fabian, thanks a lot for reaching out to the Flink community with this proposal! (Posting to the ML instead of creating a JIRA is a good idea for such questions -- you can create a ticket/tickets once the discussion here has come to a conclusion) I have two comments: - You are listing

[jira] [Created] (FLINK-8035) Unable to submit job when HA is enabled

Robert Metzger created FLINK-8035: - Summary: Unable to submit job when HA is enabled Key: FLINK-8035 URL: https://issues.apache.org/jira/browse/FLINK-8035 Project: Flink Issue Type: Bug

Re: [VOTE] Release Apache Flink-shaded 2.0 (RC1)

+1 - Checked files in staging repository - version 2.0 set correctly in the poms - jackson jar looks good - flink shaded netty contains the netty router license (including the copyright statement) - Checked the files in the RC directory - md5 sum is correct - src archive doesn't contain

[jira] [Created] (FLINK-7565) Add support for HTTP 1.1 (Chunked transfer encoding) to Flink web UI

Robert Metzger created FLINK-7565: - Summary: Add support for HTTP 1.1 (Chunked transfer encoding) to Flink web UI Key: FLINK-7565 URL: https://issues.apache.org/jira/browse/FLINK-7565 Project: Flink

Re: [DISCUSS] Stop serving docs for Flink version prior to 1.0

Please go ahead +1 Thank you for taking care! On Tue, Aug 22, 2017 at 6:02 PM, Aljoscha Krettek wrote: > +1 > > On 22. Aug 2017, at 18:01, Stephan Ewen wrote: > > > > +1 > > > > On Tue, Aug 22, 2017 at 5:58 PM, Ufuk Celebi wrote: > > >

Re: [ANNOUNCE] Flink Forward Berlin (11-13 Sep 2017) Call for Submissions is open now

ue, May 30, 2017 at 11:10 AM, Robert Metzger <rmetz...@apache.org> wrote: > Dear Flink Community, > > The Call for Submissions for Flink Forward Berlin 2017 is open now! > > Since we believe in collaboration, participation and exchange of ideas, we > are inviting the Flink c

Re: [VOTE] Release Apache Flink-shaded 1.0 (RC1)

Thanks a lot for preparing the release artifacts. While checking the source repo / release commit, I realized that you are not following the versioning scheme as flink: the current master has a "x.y-SNAPSHOT" version, and release candidates (and releases) get a x.y.z version. I wonder if it makes

Re: [DISCUSS] First release of flink-shaded

+1 to go ahead with a release. I can offer to take care of all the PMC-related actions in the release process. On Mon, Jul 3, 2017 at 6:50 PM, Aljoscha Krettek wrote: > Yes, that’s definitely possible. I was referring to the fact that this > would break the user-facing

[ANNOUNCE] New Flink PMC member: Tzu-Li (Gordon) Tai

Hi Everybody, On behalf of the Flink PMC, I'm very excited to announce Gordon as the latest addition to the Flink PMC. Gordon is a very active community member, helping with a lot of the release tasks, project discussions and of course work on the codebase itself. Regards, Robert

Re: [DISCUSS] FLIP proposal for Model Serving over Flink

Big +1 from my side on getting this effort started. Users have asked for this and I would like to see some progress there. Did anybody submit a talk about the ML efforts to Flink Forward Berlin this year? On Fri, Jun 30, 2017 at 6:04 PM, Fabian Hueske wrote: > Yes, I know

[jira] [Created] (FLINK-7007) Add README to "flink-shaded.git" repository

Robert Metzger created FLINK-7007: - Summary: Add README to "flink-shaded.git" repository Key: FLINK-7007 URL: https://issues.apache.org/jira/browse/FLINK-7007 Project: Flink Issue

[ANNOUNCE] Apache Flink 1.3.1 released

The Apache Flink community is pleased to announce the release of Apache Flink 1.3.1. Apache Flink® is an open-source stream processing framework for distributed, high-performing, always-available, and accurate data streaming applications. The release is available for download at:

Re: [DISCUSS] Release 1.3.2 planning

t; > Release management is though, I'm happy to help. Are there any timelines > you have in mind? > > Haohui > On Fri, Jun 23, 2017 at 12:01 AM Robert Metzger <rmetz...@apache.org> > wrote: > > > Hi all, > > > > with the 1.3.1 release on the way, we can st

Re: [VOTE] Release Apache Flink 1.3.1 (RC2)

I've created a PR for the release announcement. I'll publish it in ~3 hours. https://github.com/apache/flink-web/pull/68 On Thu, Jun 22, 2017 at 5:59 PM, Robert Metzger <rmetz...@apache.org> wrote: > Thanks for reporting the issue. > Sadly, the 1.3.1 vote has just passed and its g

[DISCUSS] Release 1.3.2 planning

Hi all, with the 1.3.1 release on the way, we can start thinking about the 1.3.2 release. We have already one issue that should go in there: - https://issues.apache.org/jira/browse/FLINK-6964 If there are any other blockers, let us know here :) I'm wondering if there's somebody from the

Re: [VOTE] Release Apache Flink 1.3.1 (RC2)

ng) > >> > >> - verified source and binary signatures > >> - verified source and binary checksums > >> - verified LICENSEs > >> - verified NOTICEs > >> - built from source > >> > >> Greg > >> > >> On Jun 21, 2017,

[RESULT][VOTE] Release Apache Flink 1.3.1 (RC2)

ry signatures >> - verified source and binary checksums >> - verified LICENSEs >> - verified NOTICEs >> - built from source >> >> Greg >> >> On Jun 21, 2017, at 3:46 AM, Robert Metzger <rmetz...@apache.org> wrote: >>> >>> Dear Fli

Re: How to increase Travis CI time limit

ot a problem on our side though, that's a fact by now. Branches > that haven't been > modified, like the release-1.2 branch, now also time out. > > That said, if both travis and we haven't changed anything, maybe > Apache/Infra had > anything to do with it? > > > On

Re: How to increase Travis CI time limit

Hi Chesnay, Thanks a lot for taking care of the issue! Did you get any insights by talking to the travis support about this? On Tue, Jun 13, 2017 at 5:07 PM, Chesnay Schepler wrote: > Hello, > > there currently isn't a good workaround for contributors. > > I'm currently

Re: [DISCUSS] GitBox

+1 for trying out Gitbox! On Sun, Jun 18, 2017 at 6:50 PM, Greg Hogan wrote: > My understanding is that with GitBox project committers who have linked > Apache and GitHub accounts are given organization write permissions. Other > contributors will continue to have read

Re: [VOTE] Release Apache Flink 1.3.1 (RC2)

contain any binaries - checked (some) md5sums for correctness [1] https://github.com/aljoscha/FliRTT/blob/master/test-flink.sh#L36 On Wed, Jun 21, 2017 at 5:06 PM, Robert Metzger <rmetz...@apache.org> wrote: > I see that this is an issue we should address, but on the other hand, > the

Re: [VOTE] Release Apache Flink 1.3.1 (RC2)

ata-artisans.com > wrote: > Hi, > > I suggest to include https://issues.apache.org/jira/browse/FLINK-6964 < > https://issues.apache.org/jira/browse/FLINK-6964> to the release. > > Best, > Stefan > > > Am 21.06.2017 um 09:46 schrieb Robert Metzger <rmetz

Re: [DISCUSS] Changing Flink's shading model

are separate (since > flink-shaded isn't part of Flink build > process, has a separate release process and changes to it will /never > /require immediate changes to Flink) > it seems like a very good candidate to move it into a separate repo. > > > On 21.06.2017 11:26, Robert Met

Re: [DISCUSS] Changing Flink's shading model

Its not completely clear to me how we want to version the shaded dependencies, and where we are putting them. One concern are the official apache release rules. If we want to release something to maven central, we need to do a proper vote over a source archive. I would propose to create a new

[VOTE] Release Apache Flink 1.3.1 (RC2)

Dear Flink community, Please vote on releasing the following candidate as Apache Flink version 1.3.1. The commit to be voted on: *http://git-wip-us.apache.org/repos/asf/flink/commit/1ca6e5b6 * Branch: release-1.3.1-rc2 The release

Re: [DISCUSS] Release Apache Flink 1.3.1

gt; > Timo > > > > > > Am 19.06.17 um 17:00 schrieb jincheng sun: > > > > Thanks @Timo! > > > > > > > > 2017-06-19 22:02 GMT+08:00 Timo Walther <twal...@apache.org>: > > > > > > > >> I'm working on https:/

Re: [DISCUSS] Release Apache Flink 1.3.1

Fabian and SunJincheng, it looks like we are cancelling the 1.3.1 RC1. So there is the opportunity to get the two mentioned JIRAs in. On Wed, Jun 14, 2017 at 4:16 PM, Robert Metzger <rmetz...@apache.org> wrote: > I've closed my emails, so I didn't see your messages anymore Fabian.

Re: [VOTE] Release Apache Flink 1.3.1

case > > > > > classes, Either, Try, etc.) can restore from savepoints taken with > > > Flink > > > > > 1.2.1 & 1.3.1. Tested with Scala 2.10 & 2.11. > > > > > - Tested restore of POJO types as state, behavior & error messages &g

Re: [DISCUSS] Release Apache Flink 1.3.1

> it > > > > >>> from > > > > >>>> a different process). > > > > >>>> > > > > >>>> Cheers, > > > > >>>> Till > > > > >>>> > > > > >>>>

[VOTE] Release Apache Flink 1.3.1

Dear Flink community, Please vote on releasing the following candidate as Apache Flink version 1.3.1. The commit to be voted on: http://git-wip-us.apache.org/repos/asf/flink/commit/7cfe62b9 Branch: release-1.3.1-rc1 The release artifacts to be voted on can be found at:

Re: [DISCUSS] Release Apache Flink 1.3.1

like to raise another potential blocker: it’s > currently > > not > > >>>>> easily possible for users to start a job in local mode in the IDE > > and to > > >>>>> then interact with that cluster, say for experimenting with > queryable > > >&

Re: [POLL] Who still uses Java 7 with Flink ?

ready, but what this data does not > include is all the potential future users, > i.e. slower moving organizations (banks etc.) which could be on Java 7 > still. > > Whether those are relevant is up for debate. > > Cheers, > Theo > > On Thu, Mar 23, 2017 at 12:14 PM,

Re: FlinkML on slack

I'm happy to see efforts towards machine learning on Apache Flink within the community! I think its okay to have a GitHub repository for the ML stuff, but there are some rules by the ASF you have to follow: https://www.apache.org/foundation/marks/faq/#products As immediate steps, I would remove

Re: [DISCUSS] TravisCI auto cancellation

I think auto cancellation is also enabled for branch builds. I think this is pretty bad to find out which commit introduced a build instability. I'll contact INFRA to check this again. On Wed, Mar 29, 2017 at 3:33 PM, Greg Hogan wrote: > Wow, that was a quick response that

Re: [DISCUSS] Release Apache Flink 1.3.1

oints. > > In turn, I’ve included https://issues.apache.org/jira/browse/FLINK-6804 as > a 1.3.1 blocker. > > > On 2 June 2017 at 5:27:18 PM, Nico Kruber (n...@data-artisans.com) wrote: > > while fixing build issues - what about FLINK-6654? > > On Friday, 2 June 2017

Re: [DISCUSS] Release Apache Flink 1.3.1

rts > job in HA even if NoRestartStrategy is set) also be included? > > > On 2 June 2017 at 11:21:33 AM, Robert Metzger (rmetz...@apache.org) wrote: > > I agree with both! > > I've attached a label to all JIRAs for the 1.3.1 release. Once this list > has 0 ope

[jira] [Created] (FLINK-6815) Javadocs don't work anymore in Flink 1.4-SNAPSHOT

Robert Metzger created FLINK-6815: - Summary: Javadocs don't work anymore in Flink 1.4-SNAPSHOT Key: FLINK-6815 URL: https://issues.apache.org/jira/browse/FLINK-6815 Project: Flink Issue Type

Re: [DISCUSS] Release Apache Flink 1.3.1

> We should give a good error message when the state migration fails as > described in FLINK-6742. > > > On 02.06.2017 11:05, Robert Metzger wrote: > >> Hi devs, >> >> I would like to release Apache Flink 1.3.1 with the following fixes: >> >> - FLIN

Re: [DISCUSS] Planning Release 1.4

fixes and minor features which > had been reviewed but were still queued. There did not look to be much new > development merged to master between the freezes. > > Greg > > > > On Jun 1, 2017, at 11:26 AM, Robert Metzger <rmetz...@apache.org> wrote: > > > > Hi

[DISCUSS] Planning Release 1.4

Hi all, Flink 1.2 was released on February 2, Flink 1.3 on June 1, which means we've managed to release Flink 1.3 in almost exactly 4 months! For the 1.4 release, I've put the following deadlines into the wiki [1]: *Next scheduled major release*: 1.4.0 *Feature freeze (branch forking)*: 4.

[ANNOUNCE] Apache Flink 1.3.0 released

The Apache Flink community is pleased to announce the release of Apache Flink 1.3.0. Apache Flink® is an open-source stream processing framework for distributed, high-performing, always-available, and accurate data streaming applications. The release is available for download at:

[jira] [Created] (FLINK-6798) Remove/update documentation about network buffer tuning

Robert Metzger created FLINK-6798: - Summary: Remove/update documentation about network buffer tuning Key: FLINK-6798 URL: https://issues.apache.org/jira/browse/FLINK-6798 Project: Flink

Re: Willing to contribute to Flink!

Hi, you don't need to file an ICLA. Can you please subscribe to the dev@flink.apache.org mailing list by sending an empty email to dev-subscr...@flink.apache.org? So far, your messages were manually accepted. On Thu, Jun 1, 2017 at 2:27 PM, jinchul wrote: > Hello, > > Thanks

Re: [VOTE] Release Apache Flink 1.3.0 (RC3)

Hi Timo, I agree that not having the documentation available for the new features is not good. I'll do a pass over all the open documentation PRs and try to merge as many as possible. If I have the feeling, that we have enough docs, I'll release 1.3.0. For the table API, I can put a note into the

[RESULT][VOTE] Release Apache Flink 1.3.0 (RC3)

Thanks a lot for all your responses on the point Till raised. It seems that we have an agreement to release this RC as Flink 1.3.0. I'll include a note into the release announcement regarding the state descriptor issue. Thanks also for all the release testing and the votes. +1 votes: - Chesnay

<    4   5   6   7   8   9   10   11   12   13   >