+1 for this proposal. I have a lot of desired topics in table and batch. I also second Seth and Stephan 's comment separate this in a clear way. Have concerns that maybe easy to confuse new users. If I am a beginner and find a bunch of deep documents, I need to further distinguish which is effective and which is invalid for me, which may cause me a lot of trouble.
Best, Jingsong Lee On Tue, Mar 3, 2020 at 6:36 PM Flavio Pompermaier <pomperma...@okkam.it> wrote: > Big +1 from my side. I'd be very interested in what Jeff proposed, in > particular everything related to client part (job submission, workflow > management, callbacks on submission/success/failure, etc). > Something I can't find anywhere is also how to query Flink states..would it > be possible to have something like the Presto UI [1]? Does Flink implement > some sort of query queuing? I heard about a query proxy server but I don't > know if there's a will to push in that direction. > For Stateful Functions it would be nice to deeply compare the taxi driver > solution with a more common implementation (i.e. using a database to > persist the legal data..is it safe to keep them as a Flink state?). > [1] https://www.tutorialspoint.com/apache_presto/images/web_interface.jpg > > Best, > Flavio > > On Tue, Mar 3, 2020 at 10:47 AM Jeff Zhang <zjf...@gmail.com> wrote: > > > +1 for this proposal. I am preparing some articles for how to use Flink > on > > Zeppelin, although it is not closely related with this topic, but should > be > > helpful for users to get started with Flink. > > > > Till Rohrmann <trohrm...@apache.org> 于2020年3月3日周二 下午5:39写道： > > > > > I like the idea. +1 from my side. > > > > > > Potential topics: > > > - Scheduling > > > - Cluster partitions > > > - Memory configuration > > > - Recovery > > > > > > Cheers, > > > Till > > > > > > On Tue, Mar 3, 2020 at 3:56 AM Xintong Song <tonysong...@gmail.com> > > wrote: > > > > > > > Big +1. Thanks for the idea, Arvid. > > > > > > > > I'd be excited to read such blogs. > > > > > > > > And we would also be happy to contribute some contents on the newest > > > > efforts from our team. > > > > Potential topics: > > > > - Memory configuration > > > > - Active Kubernetes integration > > > > - GPU support > > > > - Pluggable (dynamic) slot allocation > > > > > > > > Thank you~ > > > > > > > > Xintong Song > > > > > > > > > > > > > > > > On Tue, Mar 3, 2020 at 9:59 AM Benchao Li <libenc...@gmail.com> > wrote: > > > > > > > > > +1 for this proposal. As a contributor, it would be very helpful to > > > have > > > > > such blogs for us to understand status and future of Flink. > > > > > > > > > > Robert Metzger <rmetz...@apache.org> 于2020年3月3日周二 上午6:00写道： > > > > > > > > > > > I would be excited to read such a blog (can I request topics? :) > ) > > > > > > > > > > > > We could start very low key by using our wiki's blog feature: > > > > > > > > > > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/pages/viewrecentblogposts.action?key=FLINK > > > > > > > > > > > > On Mon, Mar 2, 2020 at 8:26 PM Stephan Ewen <se...@apache.org> > > > wrote: > > > > > > > > > > > > > Great idea, but I also second Seth's comment to separate this > in > > a > > > > > clear > > > > > > > way. It's easy to confuse new / potential users. > > > > > > > > > > > > > > On Mon, Mar 2, 2020 at 8:15 PM Seth Wiesman < > sjwies...@gmail.com > > > > > > > > wrote: > > > > > > > > > > > > > > > +1 on the idea. > > > > > > > > > > > > > > > > My only request would be they are clearly marked as being > about > > > > > > > internals / > > > > > > > > for advanced users to not give typical users the wrong > > impression > > > > > about > > > > > > > how > > > > > > > > much they need to understand to use Flink. Nico's network > stack > > > > blog > > > > > > post > > > > > > > > does this well[1]. > > > > > > > > > > > > > > > > Seth > > > > > > > > > > > > > > > > [1] > > https://flink.apache.org/2019/06/05/flink-network-stack.html > > > > > > > > > > > > > > > > On Mon, Mar 2, 2020 at 10:39 AM Ufuk Celebi <u...@apache.org> > > > > wrote: > > > > > > > > > > > > > > > > > I'd be happy to read such a blog. Big +1 as a potential > > reader. > > > > ;-) > > > > > > > > > > > > > > > > > > – Ufuk > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Mar 2, 2020 at 11:53 AM Arvid Heise < > > > ar...@ververica.com > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Dear devs, > > > > > > > > > > > > > > > > > > > > development speed of Flink has steadily increased. Lots > of > > > new > > > > > > > concepts > > > > > > > > > are > > > > > > > > > > introduced and technical debt removed. However, it's hard > > to > > > > keep > > > > > > > track > > > > > > > > > of > > > > > > > > > > these things if you are not directly involved. Especially > > for > > > > new > > > > > > > > > > contributors, it's often not easy to know what the best > > > > practices > > > > > > are > > > > > > > > or > > > > > > > > > if > > > > > > > > > > there are related work streams going on. > > > > > > > > > > > > > > > > > > > > In the runtime team, we had the idea to set up a dev blog > > > where > > > > > we > > > > > > > > could > > > > > > > > > > introduce newest developments. The scope should be expert > > > users > > > > > > that > > > > > > > > > > contribute to the project. Of course, some articles may > > have > > > a > > > > > > > broader > > > > > > > > > > scope and even be linked from release notes. > > > > > > > > > > > > > > > > > > > > Examples from our team to give a more specific idea: > > > > > > > > > > * Deprecated checkpoint lock and mailbox model > > > > > > > > > > * Revised interface for two phase commit sinks and new > JDBC > > > > sink > > > > > > > > > > * N-ary input operators > > > > > > > > > > * Unaligned checkpoints > > > > > > > > > > * Operator factories > > > > > > > > > > * Plugins > > > > > > > > > > > > > > > > > > > > These articles would be less formal than a FLIP (but > could > > > link > > > > > to > > > > > > > them > > > > > > > > > to > > > > > > > > > > avoid redundancy) and focus more on how other developers > > are > > > > > > actually > > > > > > > > > > impacted by the changes. It can also be used to share > > > > experiences > > > > > > > > during > > > > > > > > > > the implementation. > > > > > > > > > > > > > > > > > > > > We would like to ask the other teams if they see a > benefit > > of > > > > > such > > > > > > a > > > > > > > > blog > > > > > > > > > > and would like to contribute. Bonus points if you could > > > provide > > > > > > > > examples > > > > > > > > > of > > > > > > > > > > your topics. > > > > > > > > > > > > > > > > > > > > Best, > > > > > > > > > > > > > > > > > > > > Arvid > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > Benchao Li > > > > > School of Electronics Engineering and Computer Science, Peking > > > University > > > > > Tel:+86-15650713730 > > > > > Email: libenc...@gmail.com; libenc...@pku.edu.cn > > > > > > > > > > > > > > > > > > -- > > Best Regards > > > > Jeff Zhang > > > -- Best, Jingsong Lee
