Hi Arvid Heise-3,
Thanks for your answer. I took this approach.
I did not want to start a new thread since I wanted to avoid "subject
duplication" :)
Regards,
Krzysztof
--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
Hi KristoffSC,
it would be better if you'd open up a new thread. It's very rare for users
to check user lists after 1 year on a regular basis.
In general, if you have a cache, you usually don't want to serialize it. So
add the cache as a field inside the respective function (rewrite a lambda
to a
Hi,
Im having the same problem now. What is your approach now after gaining
some experience?
Also do you use Spring DI to setup/initialize your jobs/process functions?
--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
In general I'd expect that every class with state that you use in Flink will be
serialised, and therefore you should be marking your classes as Serializable
and set a serialVersionUID
I have what sounds like a very similar problem to yours. I need to use a
non-serializable component in my strea
Hello everyone,
coming from the Spring/CDI world, I'm new to Flink and to streaming
processing in general and apologizing for the very basic questions. I wrote
simple Flink job with all functions inlined in the main method. The main
method has some static instance variables like HTTP client and g
