um 05:25 Uhr schrieb Chase Zhang :
> Hi there,
>
> I'm writing for knowledge about
> SerializationSchema/DeserializationSchema's concurrency safety.
>
> The problem is, I've implemented my own
> KafkaSerializationSchema/KafkaDeserializationKafka which I have added
Hi there,
I'm writing for knowledge about SerializationSchema/DeserializationSchema's
concurrency safety.
The problem is, I've implemented my own
KafkaSerializationSchema/KafkaDeserializationKafka which I have added some
internal state and object cache as to avoid heavy object(mem
intended recipient(s) is prohibited. If you receive
> this e-mail in error, please notify the sender by phone or email immediately
> and delete it!
>
> From: Fabian Hueske [mailto:fhue...@gmail.com]
> Sent: Friday, March 31, 2017 12:00 PM
> To: Radu Tudoran
> Cc: u
2017 12:00 PM
To: Radu Tudoran
Cc: user@flink.apache.org
Subject: Re: concurrency?
Hi Radu,
timers are fired in order of their time stamps.
Multiple timers on the same time are deduplicated.
if you have the following logic:
time = 1, processElement(A) -> put A in state keyed to t=1, regi
, reproduction,
> or dissemination) by persons other than the intended recipient(s) is
> prohibited. If you receive this e-mail in error, please notify the sender
> by phone or email immediately and delete it!
>
>
>
> *From:* Fabian Hueske [mailto:fhue...@gmail.com]
> *Sent:*
ohibited. If you receive this
e-mail in error, please notify the sender by phone or email immediately and
delete it!
From: Fabian Hueske [mailto:fhue...@gmail.com]
Sent: Friday, March 31, 2017 11:05 AM
To: Radu Tudoran
Cc: user@flink.apache.org
Subject: Re: concurrency?
Hi Radu,
the processEleme
other event
> arrives. In principle both the processElement function and the onTimer
> function should be triggered in the same time. My question is: is there a
> fix order to execute them? Because if any of them work just like normal
> threads, than concurrency related issues could happen when accessing the
> state.
>
>
>
normal threads, than concurrency
related issues could happen when accessing the state.
Ok thanks a lot for the confirmation! Thread-safety within operators is
absolutely helpful :)
On Thu, Apr 16, 2015 at 9:20 AM, Robert Metzger wrote:
> Hi Flavio,
>
> tl;dr: they are thread safe.
>
> making a field transient means that it is ignored when serializing the
> class. This is for examp
Hi Flavio,
tl;dr: they are thread safe.
making a field transient means that it is ignored when serializing the
class. This is for example useful when you have a non-serializable field in
your function (you have to initialize it in the open() method then).
So making it transient or not doesn't cha
Hi to all,
I have a simple question: are transient fields inside a Rich-Function
(like a RichMapPartition) thread-safe or not?
Best,
Flavio
11 matches
Mail list logo
