Great job. Stephan!
Best,
Vino
Jamie Grier 于2019年2月27日周三 上午2:27写道：
> This is awesome, Stephan! Thanks for doing this.
>
> -Jamie
>
>
> On Tue, Feb 26, 2019 at 9:29 AM Stephan Ewen wrote:
>
>> Here is the pull request with a draft of the roadmap:
>>
This is awesome, Stephan! Thanks for doing this.
-Jamie
On Tue, Feb 26, 2019 at 9:29 AM Stephan Ewen wrote:
> Here is the pull request with a draft of the roadmap:
> https://github.com/apache/flink-web/pull/178
>
> Best,
> Stephan
>
> On Fri, Feb 22, 2019 at 5:18 AM Hequn Cheng wrote:
>
>>
Here is the pull request with a draft of the roadmap:
https://github.com/apache/flink-web/pull/178
Best,
Stephan
On Fri, Feb 22, 2019 at 5:18 AM Hequn Cheng wrote:
> Hi Stephan,
>
> Thanks for summarizing the great roadmap! It is very helpful for users and
> developers to track the direction
Hi Stephan,
Thanks for summarizing the great roadmap! It is very helpful for users and
developers to track the direction of Flink.
+1 for putting the roadmap on the website and update it per release.
Besides, would be great if the roadmap can add the UpsertSource
feature(maybe put it under
Hi Stephan,
Yes. I completely agree. Jincheng & Jark gave some very valuable feedbacks
and suggestions and I think we can definitely move the conversation forward
to reach a more concrete doc first before we put in to the roadmap. Thanks
for reviewing it and driving the roadmap effort!
--
Rong
Hi Shaoxuan!
I think adding the web UI improvements makes sense - there is not much open
to discuss there. Will do that.
For the machine learning improvements - that is a pretty big piece and I
think the discussions are still ongoing. I would prefer this to advance a
bit before adding it to the
Hi Rong Rong!
I would add the security / kerberos threads to the roadmap. They seem to be
advanced enough in the discussions so that there is clarity what will come.
For the window operator with slicing, I would personally like to see the
discussion advance and have some more clarity and
Hi Stephan,
Thanks for summarizing the work into a roadmap. It really helps
users to understand where Flink will forward to. The entire outline looks
good to me. If appropriate, I would recommend to add another two attracting
categories in the roadmap.
*Flink ML Enhancement*
- Refactor ML
Thanks Stephan for the proposal and a big +1 to this!
I also think it's a good idea to add a link of discussion/FLIP/JIRA to each
item as Zhijiang mentioned above.
This would be a great help for keeping track of progress and joining in the
discussion easily.
Best,
Jark
On Fri, 15 Feb 2019 at
Hi Stephan,
Thanks for the clarification! You are right, we have never initiated a
discussion about supporting OVER Window on DataStream, we can discuss it in
a separate thread. I agree with you add the item after move the discussion
forward.
+1 for putting the roadmap on the website.
+1 for
of the interested one and handle the progress of it.
Best,
Zhijiang
--
From:Jeff Zhang
Send Time:2019年2月14日(星期四) 18:03
To:Stephan Ewen
Cc:dev ; user ; jincheng sun
; Shuyi Chen ; Rong Rong
Subject:Re: [DISCUSS] Adding a mid-term
Hi Stephan,
Thanks for the clarification, yes I think these issues has already been
discussed in previous mailing list threads [1,2,3].
I also agree that updating the "official" roadmap every release is a very
good idea to avoid frequent update.
One question I might've been a bit confusion is:
I think the website is better as well.
I agree with Fabian that the wiki is not so visible, and visibility is the
main motivation.
This type of roadmap overview would not be updated by everyone - letting
committers update the roadmap means the listed threads are actually
happening at the moment.
Hi,
I like the idea of putting the roadmap on the website because it is much
more visible (and IMO more credible, obligatory) there.
However, I share the concerns about frequent updates.
It think it would be great to update the "official" roadmap on the website
once per release (-bugfix
Hi Stephan,
Thanks for this proposal. It is a good idea to track the roadmap. One
suggestion is that it might be better to put it into wiki page first.
Because it is easier to update the roadmap on wiki compared to on flink web
site. And I guess we may need to update the roadmap very often at the
Thanks Jincheng and Rong Rong!
I am not deciding a roadmap and making a call on what features should be
developed or not. I was only collecting broader issues that are already
happening or have an active FLIP/design discussion plus committer support.
Do we have that for the suggested issues as
Thanks Stephan for the great proposal.
This would not only be beneficial for new users but also for contributors
to keep track on all upcoming features.
I think that better window operator support can also be separately group
into its own category, as they affects both future DataStream API and
Very excited and thank you for launching such a great discussion, Stephan !
Here only a little suggestion that in the Batch Streaming Unification
section, do we need to add an item:
- Same window operators on bounded/unbounded Table API and DataStream API
(currently OVER window only exists in
Hi all!
Recently several contributors, committers, and users asked about making it
more visible in which way the project is currently going.
Users and developers can track the direction by following the discussion
threads and JIRA, but due to the mass of discussions and open issues, it is
very
19 matches
Mail list logo
