Other than increasing the ask.timeout, we've seen such failures being
caused by long GC pauses over bigger heaps. In such a case, you could
fiddle with a) enabling object reuse, or b) enabling off-heap memory (i.e.
taskmanager.memory.off-heap == true) to mitigate GC-induced issues a bit.
Hope it h
s a bug IMHO, this kind of error should be checked with and
> handler with a proper error.
>
> On Tue, Jun 21, 2016 at 11:49 AM, Martin Scholl wrote:
>
>> Hello everyone,
>>
>>
>> JDBCInputFormat of flink 1.1-SNAPSHOT fails with an NPE in
>&g
Hello everyone,
JDBCInputFormat of flink 1.1-SNAPSHOT fails with an NPE in Row.productArity:
%% snip %%
java.io.IOException: Couldn't access resultSet
at
org.apache.flink.api.java.io.jdbc.JDBCInputFormat.nextRecord(JDBCInputFormat.java:288)
at
org.apache.flink.api.java.io.jdbc.
