Hey all,
I wanted to remind everybody that we've started this nice initiative with
the "Flink Engine Room" / dev blog.
It would be great if we could start filling it with more content.
In my opinion, the blog posts can be fairly unpolished, as it's more
important to share the knowledge than to ma
Hurray! Thanks Arvid and Robert! Will ask the team here to prepare some
RocksDB backend related posts.
Best Regards,
Yu
On Mon, 9 Mar 2020 at 17:51, tison wrote:
> Thanks for your reply Robert. That sounds great.
>
> Best,
> tison.
>
>
> Robert Metzger 于2020年3月9日周一 下午5:46写道：
>
> > Hey Tison,
Thanks for your reply Robert. That sounds great.
Best,
tison.
Robert Metzger 于2020年3月9日周一 下午5:46写道：
> Hey Tison,
>
> only people we have manually given write permission to the Wiki are able to
> add a blog post. If somebody is posting something we don't want there, we
> can just revoke that pe
Hey Tison,
only people we have manually given write permission to the Wiki are able to
add a blog post. If somebody is posting something we don't want there, we
can just revoke that person's permission to write on the blog.
It is definitely something we should keep an eye on, but I don't think we
Thank Arvid & Robert for the effort. Amazing!
I'm curious the procedure a blog get posted. Follow the discussion so far
it seems any contributor can post his blog under the directory as he wishes,
is it the case?
Best,
tison.
Arvid Heise 于2020年3月9日周一 下午4:54写道：
> Dear all,
>
> Robert added a l
Dear all,
Robert added a link to the engine room blog on the Apache wiki [1]. It's
currently empty except for one test post. To add a new post, you just
create a new blog post from the top menu ("engine room" is just a fancy
link to the default blog).
Robert would like to write about the migratio
+1 on Arvid's proposal. looking forward to the "Engine Room" blog series.
:-D
--
Rong
On Sat, Mar 7, 2020 at 12:08 AM Yu Li wrote:
> +1 to Arvid's proposal, thanks for the efforts!
>
> Best Regards,
> Yu
>
>
> On Thu, 5 Mar 2020 at 23:04, Zhijiang
> wrote:
>
> > Thanks for this proposal Arvid!
+1 to Arvid's proposal, thanks for the efforts!
Best Regards,
Yu
On Thu, 5 Mar 2020 at 23:04, Zhijiang
wrote:
> Thanks for this proposal Arvid!
> +1 and looking forward to the wiki structure and more following blogs.
>
> Best,
> Zhijiang
>
>
> --
Thanks for this proposal Arvid!
+1 and looking forward to the wiki structure and more following blogs.
Best,
Zhijiang
--
From:Dian Fu
Send Time:2020 Mar. 5 (Thu.) 19:08
To:dev
Subject:Re: Flink dev blog
+1 to Arvid's proposal
>
+1 to Arvid's proposal
> 在 2020年3月5日，下午6:49，Jark Wu 写道：
>
> +1 to Arvid's proposal.
>
> On Thu, 5 Mar 2020 at 18:13, Robert Metzger wrote:
>
>> +1 to Arvid's proposal.
>>
>>
>>
>> On Thu, Mar 5, 2020 at 4:14 AM Xingbo Huang wrote:
>>
>>> Thanks a for this proposal.
>>>
>>> As a new cont
+1 to Arvid's proposal.
On Thu, 5 Mar 2020 at 18:13, Robert Metzger wrote:
> +1 to Arvid's proposal.
>
>
>
> On Thu, Mar 5, 2020 at 4:14 AM Xingbo Huang wrote:
>
> > Thanks a for this proposal.
> >
> > As a new contributor to Flink, it would be very helpful to have such
> blogs
> > for us to un
+1 to Arvid's proposal.
On Thu, Mar 5, 2020 at 4:14 AM Xingbo Huang wrote:
> Thanks a for this proposal.
>
> As a new contributor to Flink, it would be very helpful to have such blogs
> for us to understand the future of Flink and get involved
>
> BTW, I have a question whether the dev blog ne
Thanks a for this proposal.
As a new contributor to Flink, it would be very helpful to have such blogs
for us to understand the future of Flink and get involved
BTW, I have a question whether the dev blog needs a template like FLIP.
Of course, There is no doubt that dev blogs do not need to be a
I see that the majority would like to have an uncomplicated process to
publish an article first to gather feedback and then like to have polished
versions on the blog with official review process.
Then, the obvious solution is to have a process that is two-fold:
* First a draft is published and re
Big +1 for this proposal and second Ufuk's feeling!
I guess "Engine room" section in Wiki would attract lots of technical fans.:)
Best,
Zhijiang
--
From:Yu Li
Send Time:2020 Mar. 4 (Wed.) 14:42
To:dev
Cc:vthinkxie
Subject:Re: Fl
Big +1 on adding a dev blog and starting with wiki. And +1 to promote the
fully polished articles to blog web with a formal process.
The latter one also brings up another good-to-have improvement that adding
categories and navigation in our blog so people could easily find different
topics like re
I also like Ufuk's idea.
The wiki allows people to post on their works in a quick and easier way.
For me and probably many other Chinese folks, writing and polishing a
formal article in English usually takes a long time, of which a significant
portion is spent on polishing the language. If the blo
+1 for this.
Regarding to the place to hold blogs. Personally, I prefer to use existing
blog and separate by tags/categories and title names.
Because, the dev blogs are very good learning materials. I believe many
users will be interested in these posts. It's just like
"Technology Deep Dive" talks
+1 on starting with the Wiki. I really like the name "Engine room". Can we
name the section in the Wiki like that? In general, if we think that a post
or a series of posts would be a good fit for the main blog, it would be
pretty straightforward to promote a post from the Engine room to the main
bl
Big +1 on this. Some of these topics are not only for contributors, but
would also be super useful for advance users.
One topic I can think of in addition is: Security/Kerberos.
Echo on Both Seth's idea, we could have both wiki and PR submission:
As Robert mentioned - wiki submission would make th
Big +1 on this idea. It will benefit both the developers and users a lot.
Regarding to the place to hold these blogs, my preference is 3) as I notice
that there are already a few high quality blogs on flink web-site[1] and I
guess that may be a good place to start with. We just need to figure ou
Hi all
maybe we can use markdown & GitHub to make the submission easy to review
I have set up a similar blog for Flink-china blog before(deprecated), glad
to offer help if needed
here is the link: https://github.com/flink-china/doc
Seth Wiesman 于2020年3月3日周二 下午10:51写道：
> For lack of a better wa
I fully agree with Seth!
I proposed the Wiki to make the submission process as frictionless as
possible.
If we publish this on the official Flink website, we will have an
involved process of slow reviews, incorporating feedback etc., making such
a publication painful.
In the wiki, people can basi
For lack of a better way to put this, I think the location depends on the
level of effort you want to put into writing these articles.
If they are informal design documents then I think the wiki is the way to
go.
If you want to have them be more polished then the existing blog. This
means going t
I think there is enough to positive to start setting it up. That begs the
question: in which format.
Following possibilities exist:
1) Use wiki as Robert pointed out.
2) Add new blog.
3) Use existing blog and separate by tags #user, #expert, #dev (can be
mixed). Start page could filter on #user by
+1 for the idea :) And fully agree to clearly separate them.
I think the original idea was writing about some recent changes in the Flink’s
code base, that could affect other Flink developers (contributors/committers).
Like for example some new ideas/future directions that we want to follow.
Es
Thx for the good feedback. I'd like to pursue the topic.
Regarding the scope. How about we add a banner on each article that
describes the intended audience and the scope?
Example (two phase commit sink):
This article is primarily intended for Flink contributors and expert users.
Users would only
+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 effecti
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 som
+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 于2020年3月3日周二 下午5:39写道：
> I like the idea. +1 from my side.
>
> Potential topics:
> -
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 wrote:
> Big +1. Thanks for the idea, Arvid.
>
> I'd be excited to read such blogs.
>
> And we would also be happy to
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 yo
+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 于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
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 wrote:
> Great idea, but I also second Seth
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 wrote:
> +1 on the idea.
>
> My only request would be they are clearly marked as being about internals /
> for advanced users to n
+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/2
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 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 o
37 matches
Mail list logo
