Re: flink jira contributor permission

2019-03-22 Thread Jocean shi
Thanks Thomas Weise 于2019年3月23日周六 下午12:33写道： > Done! > > > On Fri, Mar 22, 2019 at 9:11 PM Jocean shi wrote: > > > Hi, > > > > I want to contribute to Apache Flink. > > Would you please give me the contributor permission? > > My JIRA ID is Jocean. > > > > Best > > Jocean.shi > > >

Re: flink jira contributor permission

2019-03-22 Thread Thomas Weise
Done! On Fri, Mar 22, 2019 at 9:11 PM Jocean shi wrote: > Hi, > > I want to contribute to Apache Flink. > Would you please give me the contributor permission? > My JIRA ID is Jocean. > > Best > Jocean.shi >

flink jira contributor permission

2019-03-22 Thread Jocean shi
Hi, I want to contribute to Apache Flink. Would you please give me the contributor permission? My JIRA ID is Jocean. Best Jocean.shi

Re: [DISCUSS] Improve the flinkbot

2019-03-22 Thread vino yang
+1 Best, Vino Bowen Li 于2019年3月23日周六 上午12:28写道： > +1, sounds good, Jark. > > On Fri, Mar 22, 2019 at 1:55 AM Fabian Hueske wrote: > > > Hi Jark, > > > > Thanks for driving the effort to integrate the Chinese website! > > > > We have the policy that new features / improvements should be documen

Re: [DISCUSS] FLIP-33: Standardize connector metrics

2019-03-22 Thread Stephan Ewen
Ignoring for a moment implementation details, this connector metrics work is a really good thing to do, in my opinion The questions "oh, my job seems to be doing nothing, I am looking at the UI and the 'records in' value is still zero" is in the top three support questions I have been asked person

Re: [DISCUSS] Improve the flinkbot

2019-03-22 Thread Bowen Li
+1, sounds good, Jark. On Fri, Mar 22, 2019 at 1:55 AM Fabian Hueske wrote: > Hi Jark, > > Thanks for driving the effort to integrate the Chinese website! > > We have the policy that new features / improvements should be documented in > the same PR for a long time. > So far, this was checked by

[jira] [Created] (FLINK-11997) ConcurrentModificationException: ZooKeeper unexpectedly modified

2019-03-22 Thread David Anderson (JIRA)
David Anderson created FLINK-11997: -- Summary: ConcurrentModificationException: ZooKeeper unexpectedly modified Key: FLINK-11997 URL: https://issues.apache.org/jira/browse/FLINK-11997 Project: Flink

[jira] [Created] (FLINK-11996) Case class maximum of 22 fields

2019-03-22 Thread Wouter Zorgdrager (JIRA)
Wouter Zorgdrager created FLINK-11996: - Summary: Case class maximum of 22 fields Key: FLINK-11996 URL: https://issues.apache.org/jira/browse/FLINK-11996 Project: Flink Issue Type: Improve

Re: Row.setField returning row itself

2019-03-22 Thread Flavio Pompermaier
You're right Chesnay, I didn't remember that .of was introduced :( Sorry! On Fri, Mar 22, 2019 at 12:35 PM Chesnay Schepler wrote: > You could even use a method reference here: "map(Row::of)" > > On 22/03/2019 12:33, Chesnay Schepler wrote: > > I can see that this would be convenient but please

Re: Row.setField returning row itself

2019-03-22 Thread Chesnay Schepler
You could even use a method reference here: "map(Row::of)" On 22/03/2019 12:33, Chesnay Schepler wrote: I can see that this would be convenient but please find a better example; yours can be solved easily using "Row.of(value)". On 22/03/2019 12:26, Flavio Pompermaier wrote: Hi all, many times

Re: Row.setField returning row itself

2019-03-22 Thread Chesnay Schepler
I can see that this would be convenient but please find a better example; yours can be solved easily using "Row.of(value)". On 22/03/2019 12:26, Flavio Pompermaier wrote: Hi all, many times I had the feeling that allowing Row.setField() to return the modified object instead of void would really

Row.setField returning row itself

2019-03-22 Thread Flavio Pompermaier
Hi all, many times I had the feeling that allowing Row.setField() to return the modified object instead of void would really make the (Java) code cleaner in a very unobtrusive way. For example, I could write something like: DataSet columnData = input.map(value -> new Row(1).setField(0, value)) in

Re: [DISCUSS] Reorganizing Table-related Jira components some more

2019-03-22 Thread Robert Metzger
Nice! I'm happy to see that the components are evolving (this means they are used :) ) This is also a good test for my latest changes to the GitHub labeling tools. They should support label changes. On Fri, Mar 22, 2019 at 10:18 AM Aljoscha Krettek wrote: > Perfect! I re-arranged the components

[jira] [Created] (FLINK-11995) Kafka09SecuredRunITCase fails due to port conflict

2019-03-22 Thread Chesnay Schepler (JIRA)
Chesnay Schepler created FLINK-11995: Summary: Kafka09SecuredRunITCase fails due to port conflict Key: FLINK-11995 URL: https://issues.apache.org/jira/browse/FLINK-11995 Project: Flink Is

Re: [DISCUSS] Reorganizing Table-related Jira components some more

2019-03-22 Thread Aljoscha Krettek
Perfect! I re-arranged the components and created some new ones to fit this. Right now, most issues are still in “Table SQL / API” I’ll start to move issues to other components but please try and have a look as well and move issues to the correct components. See here for how many issues are in

Re: [DISCUSS] Improve the flinkbot

2019-03-22 Thread Fabian Hueske
Hi Jark, Thanks for driving the effort to integrate the Chinese website! We have the policy that new features / improvements should be documented in the same PR for a long time. So far, this was checked by reviewers and committers but often overlooked or decided to add documentation in a subseque