Re: Flink CEP development is stalling

Hi Stephan! Thank you for your answer. I appreciate your efforts and I know how busy you and other Flink committers are. I am looking forward for the upcoming discussion of Flink modules! Best regards, Ivan. On Mon, 16 Jan 2017 at 11:32 Stephan Ewen wrote: > Hi Ivan! > >

Re: Flink CEP development is stalling

Hi Ivan! Thank you for bringing this thread up. I agree, we need to do something about how some modules are currently handled. The CEP library definitely needs more active committers. Adding new committers will be necessary, I think, but as you mentioned, it needs at least one (better more)

Re: Flink CEP development is stalling

Hi Alexey, I agree with you. Most contributors are overloaded, but PRs for other sub-projects are reviewed much faster. In my experience, in most cases, you can get a first review for a PR in less than a week and it's usually merged within a month or less. Flink CEP is a notable exception. I

Re: Flink CEP development is stalling

Hi Ivan, I think problem not only with CEP project. Main contributors overloaded and simple fixes frequently are staying as PR without merge. You can see how amount of open PR increasing over time. Thanks, Alexey Diomin 2017-01-15 17:18 GMT+04:00 Ivan Mushketyk : >

Re: Flink CEP development is stalling

Hi Dmitry, Your contributions are welcomed, but right now the most critical issue is that CEP project does not have an experienced Flink contributor who can review and approve new pull requests. I hope that Flink community will promptly resolve the issue, so feel free to take select a JIRA issue

Re: Flink CEP development is stalling

I would be interested to contribute to CEP. I am following Flink project, but haven't contributed yet. Next 2 weeks I am a bit busy with my work, but then I llbe happy to dig into it. I used to work in IoT so event processing is a close topic for me. Dmitry. On Fri, 13 Jan 2017 at 14:58, Ivan

Re: Flink CEP development is stalling

Hi Till, Thank you for your reply. I wonder if the following will work. What if you can find a Flink committer/committers that will review and iterate on CEP PRs before you review them. They don't need to know all CEP internals, but they will help to eradicate most of the issues. Then you will

Re: Flink CEP development is stalling

Hi Ivan, first of all let me apologise for the bad experience you've had with opening CEP PRs in the past. The general problem as you've said is that there is nobody who reviews the open PRs. I used to do this in the but at the moment I hardly find time due to other commitments. I think the way

Re: Flink CEP development is stalling

+1 I have some clientes interested in CEP features El 11/1/17 16:23, "Ivan Mushketyk" escribió: Hi Flink devs, Roughly half a year ago I implemented several PRs for Flink-CEP[1][2][3] but since then there were no progress with the reviews. What is

Flink CEP development is stalling

Hi Flink devs, Roughly half a year ago I implemented several PRs for Flink-CEP[1][2][3] but since then there were no progress with the reviews. What is frustrating about this situation is that Flink customers are asking for features in these PRs. For example customers commented on [1] and [2]