I'm obviously pro about promoting the usage of this amazing library but,
maybe, in this early stage I'd try to keep it as a separate project.
However, this really depends about how frequently the code is goin to
change..the Flink main repo is becoming more and more complex to handle due
to the incr
+1 to add Stateful Function to flink core to let it stay in the Flink
repository.
Best,
Vino
Stephan Ewen 于2019年10月14日周一 下午7:29写道：
> Thank you all for the encouraging feedback! So far the reaction to add this
> to Flink was exclusively positive, which is really great to see!
>
> To make this ha
Thank you all for the encouraging feedback! So far the reaction to add this
to Flink was exclusively positive, which is really great to see!
To make this happen, here would be the next steps:
(1) As per the bylaws, a contribution like that would need a PMC vote,
because it is a commitment to take
+1 to add Stateful Function to FLINK core repository.
Best,
tison.
Becket Qin 于2019年10月14日周一 下午4:16写道：
> +1 to adding Stateful Function to Flink. It is a very useful addition to
> the Flink ecosystem.
>
> Given this is essentially a new top-level / first-citizen API of Flink, it
> seems better
+1 to adding Stateful Function to Flink. It is a very useful addition to
the Flink ecosystem.
Given this is essentially a new top-level / first-citizen API of Flink, it
seems better to have it the Flink core repo. This will also avoid letting
this important new API to be blocked on potential probl
Hi all,
Big +1 for contributing Stateful Functions to Flink and as for the
main question at hand, I would vote for putting it in the main
repository.
I understand that this can couple the release cadence of Flink and
Stateful Functions although I think the pros of having a "you break
it,
you fix
Hi Stephan,
Big +1 for adding stateful functions to Apache Flink! The use cases unlocked
with this feature are very interesting and promising.
Regarding to whether to place it into Flink core repository, personally I
perfer to put it in the main repository. This feature introduces a new set of
Hi Stephan,
Big +1 for adding this to Apache Flink!
As for the problem of whether this should be added to the Flink main
repository, from my side, I prefer to put it in the main repository. Not
only Stateful Functions shares very close relations with the current Flink,
but also other libs or modu
Hi Stehpan,
+1 for having Stateful Functions in Flink.
Before discussing which repository it should belong, I was wondering if we
have reached an agreement of "splitting flink repository" as Piotr
mentioned or not. It seems that it's just no more further discussion.
It's OK for me to add it to co
Hi Stephan,
Big +1 for adding stateful functions to Flink. I believe a lot of user
would be interested to try this out and I could imagine how this could
contribute to reduce the TCO for business requiring both streaming
processing and stateful functions.
And my 2 cents is to put it into flink co
Hi Stephan,
bit +1 for adding this great features to Apache Flink.
Regarding where we should place it, put it into Flink core repository or
create a separate repository? I prefer put it into main repository and
looking forward the more detail discussion for this decision.
Best,
Jincheng
Jingso
Hi Stephan,
big +1 for this contribution. It provides another user interface that is
easy to use and popular at this time. these functions, It's hard for users
to write in SQL/TableApi, while using DataStream is too complex. (We've
done some stateFun kind jobs using DataStream before). With statef
Hi Stephan,
big +1 for adding statefun to Apache Flink.
I think we can add it in the main repository as a library just like State
Process API.
Having it in the main repository can closely co-develop with Apache Flink
which be beneficial for both side.
Regards,
Jark
On Fri, 11 Oct 2019 at 19:12
Hi Stephan,
+1 for adding stateful functions to Flink. I believe the new set of
applications this feature will unlock will be super interesting for new and
existing Flink users alike.
One reason for not including it in the main repository would to not being
bound to Flink's release cadence. This
+1 non-binding on contribution.
Separate repo, or feature branch to start maybe? I just feel like in the
beginning this thing is going to have lots of breaking changes that maybe
aren't going to fit well with tests / other "v1+" release code. Just my
.02.
On Fri, Oct 11, 2019 at 4:38 AM Stephan
Hi Stephan,
+1 for adding this to Apache Flink!
Regarding the question if this should be committed to the main repository or as
a separate one, I think it should be the main one. Previously we were
discussing the idea of splitting Apache Flink into multiple repositories and I
think the consen
Dear Flink Community!
Some of you probably heard it already: On Tuesday, at Flink Forward Berlin,
we announced **Stateful Functions**.
Stateful Functions is a library on Flink to implement general purpose
applications. It is built around stateful functions (who would have thunk)
that can communic
17 matches
Mail list logo
