Thanks for the update Taneli. Glad that you solved the problem. If you
should find out more about the more obscure case, let us know. Maybe there
is something we can still improve to prevent misleading exceptions in the
future.
Cheers,
Till
On Tue, Jan 1, 2019 at 3:01 PM Taneli Saastamoinen <
tan
To return to this old thing, this was basically user error. The second of
the transformations was keying by a field that was sometimes null after the
first transformation. (This was supposed to never happen, but then it did
happen in production.)
The confusing part is where the exception occurs. T
On 27 July 2018 at 19:21, Chesnay Schepler wrote:
> At first glance this looks like a bug. Is the nothing in the stack trace
after the NullPointerException?
Hmm, there is actually, sorry about that:
Caused by: java.lang.NullPointerException
at
org.apache.flink.runtime.state.KeyGroupRangeAssignme
At first glance this looks like a bug. Is the nothing in the stack trace
after the NullPointerException?
How reliably can you reproduce this?
On 27.07.2018 19:00, Taneli Saastamoinen wrote:
Morning everyone,
I'm getting the following exception in my Flink job (Flink version is
1.5.0):
java
Morning everyone,
I'm getting the following exception in my Flink job (Flink version is
1.5.0):
java.lang.RuntimeException: Exception occurred while processing valve
output watermark:
at
org.apache.flink.streaming.runtime.io.StreamInputProcessor$ForwardingValveOutputHandler.handleWatermark(Stream
