Hi all,
We discussed the matter again in our latest release planning (see [1]). We see
a lot of valid
points in this thread. As we were not able to come to a clear conclusion within
the meeting and
most of the arguments mentioned will still be valid even if we extend the
feature freeze by
a
Hi all,
Thanks Xintong for bringing this up.
I would like to share some experience of the usage of Flink in our company
(ByteDance).
1. We started building our SQL platform in mid 2019, using v1.9 blink
planner, and it's amazing.
Also we added many internal features which is still missing in
Hi all,
@Xintong Song
Thanks for reminding me, I would contact Jark to update the wiki page.
Besides, I'd like to provide more inputs by sharing our experience about
upgrading Internal version of Flink.
Flink has been widely used in the production environment since 2018 in our
company. Our
Hi all,
We are using Flink for our eventing system. Overall we are very happy with
the tech, documentation and community support and quick replies in mails.
My last 1 year experience with versions.
We were working on 1.10 initially during our research phase then we
stabilised with 1.11 as we
Thanks everyone for the feedback.
@Jing,
Thanks for the inputs. Could you please ask a committer who works together
with you on these items to fill them into the feature collecting wiki page
[1]? I assume Jark, who co-edited the flip wiki page, is working with you?
@Kurt, @Till and @Seth,
First
Hi Everyone,
+1 for the Release Managers. Thank you all for volunteering.
@Till Rohrmann A common sentiment that I have heard
from many users is that upgrading off of 1.9 was very difficult. In
particular, a lot of people struggled to understand the new memory model.
Many users who required
Thanks for volunteering as our release managers Xintong, Dawid and Joe!
Thanks for starting the discussion about the release date Kurt. Personally,
I prefer in general shorter release cycles as it allows us to deliver
features faster and people feel less pressure to merge half-done features
last
Thanks for bringing this up.
I have one thought about the release period. In a short word: shall we try
to extend the release period for 1 month?
There are a couple of reasons why I want to bring up this proposal.
1) I observed that lots of users are actually far behind the current Flink
Hi Dawid, Joe & Xintong,
Thanks for starting the discussion.
I would like to polish Window TVFs[1][2] which is a popular feature in SQL
introduced in 1.13.
The detailed items are as follows.
1. Add more computations based on Window TVF
* Window Join (which is already merged in master
Hi all,
As 1.13 has been released for a while, I think it is a good time to start
planning for the 1.14 release cycle.
- Release managers: This time we'd like to have a team of 3 release
managers. Dawid, Joe and I would like to volunteer for it. What do you
think about it?
- Timeline: According
10 matches
Mail list logo
