nt for expected behavior.
>
>
>
> Seth
>
>
>
> *From: *Stephan Ewen <se...@apache.org>
> *Date: *Monday, October 9, 2017 at 2:44 PM
> *To: *Kostas Kloudas <k.klou...@data-artisans.com>
> *Cc: *Colin Williams <colin.williams.seat...@gmail.com>, user <
>
at...@gmail.com>, user
<user@flink.apache.org>
Subject: Re: serialization error when using multiple metrics counters
Interesting, is there a quirk in Scala that using multiple lazy variables
results possibly in eager initialization of some?
On Mon, Oct 9, 2017 at 4:37 PM, Kostas Kloudas
<
Interesting, is there a quirk in Scala that using multiple lazy variables
results possibly in eager initialization of some?
On Mon, Oct 9, 2017 at 4:37 PM, Kostas Kloudas
wrote:
> Hi Colin,
>
> Are you initializing your counters from within the open() method of you
Hi Colin,
Are you initializing your counters from within the open() method of you rich
function?
In other words, are you calling
counter = getRuntimeContext.getMetricGroup.counter(“my counter”)
from within the open().
The counter interface is not serializable. So if you instantiate the
I've created a RichMapFunction in scala with multiple counters like:
lazy val successCounter = getRuntimeContext.
getMetricGroup.counter("successfulParse")
lazy val failedCounter = getRuntimeContext.
getMetricGroup.counter("failedParse")
lazy val errorCounter = getRuntimeContext.