You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by ziv <zi...@elbitsystems.com> on 2017/09/26 08:20:06 UTC
RE: is flink' states functionality futile?
hi Tzu-Li,
sorry I have to reopen it but I'm still having troubles with using data from
previous records.
you said:
“If that’s the case, and you don’t care about losing state on failures and
don’t care about at-least-once / exactly-once, then yes you don’t have to
use the managed state APIs in Flink.
You can just have ordinary fields to achieve this since Flink’s streaming
operators are basically long-running processes that continuously process
events in the stream and manipulates its state.”
look that if one of my fields is of unserializable type, then:
if I mark it as transient, then its value erased and I get null pointer
exception.
on the other hand, leave it without 'transient', it's a compilation error -
implementation of function is not serializable.
how you explain that?
Best, Ziv.
--
Sent from: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/