I think Travis will fix this hickup soon. Maybe you could provide them
with the stuck builds in a mail to supp...@travis-ci.com.
On Fri, Oct 9, 2015 at 3:39 PM, Sachin Goel wrote:
> Found another one: https://travis-ci.org/apache/flink/jobs/84473635
>
> -- Sachin Goel
> Computer Science, IIT Delh
Found another one: https://travis-ci.org/apache/flink/jobs/84473635
-- Sachin Goel
Computer Science, IIT Delhi
m. +91-9871457685
On Fri, Oct 9, 2015 at 7:06 PM, Sachin Goel
wrote:
> These two builds are stuck on travis. It seems to a travis issue and is
> limiting the number of concurrent build
These two builds are stuck on travis. It seems to a travis issue and is
limiting the number of concurrent builds to 3.
https://travis-ci.org/apache/flink/jobs/84317317
https://travis-ci.org/apache/flink/jobs/84405887
Perhaps someone from infra should cancel them.
-- Sachin Goel
Computer Science,
I think that's actually very use case specific.
You're code will never see the malformed record because it is dropped by
the input format.
Other applications might rely on complete input and would prefer an
exception to be notified about invalid input.
Flink's CsvInputFormat has a parameter "lenie
