Hi all,
I’m going to be at Scale by the Bay later this week, and am looking forward to
hearing about Flink during the formal talks.
But I was wondering if anyone knows whether there will also be informal
talks/meetups on Flink during the event.
Thanks,
— Ken
--
Ken Kr
Hi,
I'm running a Flink application where data are retrieved from a Kafka broker
and forwarded to a Cassandra sink.
I've implemented the following watermark emitter:
public class CustomTimestampExtractor implements
AssignerWithPeriodicWatermarks>{
private final long maxOutOfOrderness = 800;
Great to hear that you got it working :-) Looking forward to your blog post
to learn more about your experiences :-)
Cheers,
Till
On Fri, Nov 10, 2017 at 10:18 PM, Vergilio, Thalita <
t.vergilio4...@student.leedsbeckett.ac.uk> wrote:
> Hi Til,
>
>
> Thank you very much for that. And thanks for y
Hello M Singh,
If you check the comment at the beginning of the file, it said
Forwarding elements, watermarks, or status status elements must be protected
by synchronizing
* on the given lock object. This ensures that we don't call methods on a
* {@link OneInputStreamOperator} conc
Thanks Kien/Jorn:
I see the code for processElement being called with a lock but did not see that
the timer based invocation is synchronized by the same lock. Does that mean
that I should use synchonization in my code and how will that impact the
performance ? Please let me know if you have
Be careful though with racing conditions .
> On 12. Nov 2017, at 02:47, Kien Truong wrote:
>
> Hi Mans,
>
> They're not executed in the same thread, but the methods that called them are
> synchronized[1] and therefore thread-safe.
>
> Best regards,
>
> Kien
>
> [1]
> https://github.com/apa
