> 2017-07-12
>
> hzyuemeng1
>
>
>
> 发件人："wenlong.lwl" <wenlong88@gmail.com>
> 发送时间：2017-07-05 10:27
> 主题：Re: [DISCUSS] FLIP-22: Eager State Declaration
> 收件人："dev"<dev@flink.apache.org>
> 抄送：
>
> Hi, all, we have jobs which
pengwenlong?
2017-07-12
hzyuemeng1
发件人："wenlong.lwl" <wenlong88@gmail.com>
发送时间：2017-07-05 10:27
主题：Re: [DISCUSS] FLIP-22: Eager State Declaration
收件人："dev"<dev@flink.apache.org>
抄送：
Hi, all, we have jobs which create state according to type of the
Hi all,
Thanks for the proposal I definitely see the value in making eager
registration as a requirement for several features that you mentioned
(mostly related to state serialization/format etc.).
The only problem I see which has been mentioned by others is that the lack
of lazy (dynamic) state
Hi Tzu-Li,
Thanks for the proposal. The changes are great. I have several questions
about some details.
First, do you have any plan to provide a method to remove states? Now
states can only be created (either lazily or eagerly), but cannot be
removed. We cannot remove those states not registered
Hi, all, we have jobs which create state according to type of the key and a
dynamic configuration:
eg: key_type_1's aggregation function is average, while key_type_2's is sum
we need to create state dynamically because the aggregation function may
change in runtime and different aggregation
Could you add an example to the FLIP for how a user can register a state
with the methods in the RichFunction interface?
Currently it only contains an example for the annotation option.
These methods look like they are called by the user, but that doesn't
really make sense to me as after all
