Hello Gyula & Stefan,
Below I attach a similar situation that I am trying to resolve, [1]
I am also using *managed operator state*, but I have some trouble with the
flink documentation. I believe it is not that clear.
So, I have the following questions:
1 -- Can I concatenate all the partial sta
Hi,
+1 to what Stefan is suggesting , we have been using similar logic for a
while:
@Override
public void snapshotState(StateSnapshotContext context) throws Exception {
updateBroadcastState();
super.snapshotState(context);
}
@Override
public void initializeState(StateInitialization
What I mean is that you could obtain such a state in
initializeState(FunctionInitializationContext context) {
context.getOperatorStateStore().getUnionListState(…);
}
and in snapshotState(…), you will just insert the state in only one of the
parallel instances. Which instance can be base
Thanks Fabian, I'll keep an eye to that JIRA.
I'm not sure I follow you Stefan. You mean that I could implement my own
OperatorStateStore and override its methods (e.g. snapshot and restore) to
achieve this functionality? I think I don't have enough knowledge about
Flink's internals to implement t
Hi,
I think you can do this already, please take a look at
OperatorStateStore::getUnionListState(…). You could add state to this only one
one parallel operator instance, e.g. by checking the subtask index.
Best,
Stefan
> Am 03.07.2017 um 18:14 schrieb Fabian Hueske :
>
> Hi Gerard,
>
> such
Hi Gerard,
such a type of state is not yet supported, but on the roadmap.
The feature is called Broadcast State. A description is in JIRA [1].
Best, Fabian
[1] https://issues.apache.org/jira/browse/FLINK-4940
2017-07-03 17:50 GMT+02:00 gerardg :
> Hello,
>
> Is it possible to have managed oper
