optimiser, which
in turn might depend on data volumes, pojo structures etc.
In any case, errors like this can of course be easily detected and fixed
with proper unit tests, whereas I didn't originally have quite full
coverage for unexpected partially-null data.
Cheers,
On Mon, 30 Jul 2018 a
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
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
