I solved the problem by passing the HLL object to the function, updating it
and returning it as new state. This was obviously a thinking barrier... ;-)
--
View this message in context:
http://apache-spark-user-list.1001560.n3.nabble.com/Sharing-object-state-accross-transformations
Does anybody have a hint for me? Maybe its too trivial to see for me and I'm
blind. Please give me some advice.
--
View this message in context:
http://apache-spark-user-list.1001560.n3.nabble.com/Sharing-object-state-accross-transformations-tp25544p25655.html
Sent from the Apache Spark
ending the Accumulator class (in
>>> Java)? I
>>> also read that for transformations this only should be used for debugging
>>> purposes...
>>>
>>> So how can I achive to use one global defined HLL-object in a spark
>>> stream
>>> transformation? I a
am with addAccumulator,
> addInPlace
> and zero?
>
> Thanks in advance for your help and your advice!
>
>
>
>
> --
> View this message in context:
> http://apache-spark-user-list.1001560.n3.nabble.com/Sharing-object-state-accross-transformations-tp25544.html
>
xt:
http://apache-spark-user-list.1001560.n3.nabble.com/Sharing-object-state-accross-transformations-tp25544.html
Sent from the Apache Spark User List mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: user-unsubscr.
