RE: FLINK-13497 / "Could not create file for checking if truncate works" / HDFS

Hi, FYI we've switched to a different Hadoop server, and the issue vanished... It does look as the cause was on hadoop side. Thanks again Congxian.Adrian    - Original message -From: "Adrian Vasiliu" To: qcx978132...@gmail.comCc: user@flink.apache.orgSubject: [EXTERNAL] RE: F

RE: FLINK-13497 / "Could not create file for checking if truncate works" / HDFS

in various answers, in particular the one about temp files. Thanks Adrian   - Original message -From: Congxian Qiu To: Adrian Vasiliu Cc: user Subject: [EXTERNAL] Re: FLINK-13497 / "Could not create file for checking if truncate works" / HDFSDate: Tue, Oct 15, 2019 4:02 AM 

FLINK-13497 / "Could not create file for checking if truncate works" / HDFS

.Any lights about:1/ Would you confirm that our stack trace is related with  https://issues.apache.org/jira/browse/FLINK-13497  ?2/ Any ETA for a 1.9.x fixing it?  Thanks Adrian Vasiliu

Re: ElasticsearchSink in Flink 1.4.0 with Elasticsearch 5.2+

OK, thanks a lot Fabian. Adrian   - Original message -From: Fabian Hueske <fhue...@gmail.com>To: Adrian Vasiliu <vasi...@fr.ibm.com>Cc: user <user@flink.apache.org>Subject: Re: ElasticsearchSink in Flink 1.4.0 with Elasticsearch 5.2+Date: Mon, Jan 22, 2018 2:54 PM 

ElasticsearchSink in Flink 1.4.0 with Elasticsearch 5.2+

Hello,   With a local run of Flink 1.4.0, ElasticsearchSink fails for me with a local run of Elasticsearch 5.6.4 and 5.2.1, while the same code (with adjusted versions of dependencies) works fine with Elasticsearch 2.x (tried 2.4.6). I get:java.lang.NoSuchMethodError:

Re: Unrecoverable job failure after Json parse error?

to implement custom handling is okay... Thanks Adrian   - Original message -From: Nico Kruber <n...@data-artisans.com>To: Adrian Vasiliu <vasi...@fr.ibm.com>Cc: user@flink.apache.orgSubject: Re: Unrecoverable job failure after Json parse error?Date: Tue, Jan 16, 2018 3:18 PM  Ni

Re: Unrecoverable job failure after Json parse error?

mprovement for JSONKeyValueDeserializationSchema to provide this behaviour as an out-of-the-box option. But anyway, I do have a solution in hands. Thanks again. Adrian   - Original message -From: Nico Kruber <n...@data-artisans.com>To: Adrian Vasiliu <vasi...@fr.ibm.com>, user@flink.apache.orgCc:Subject: Re: Unr

Unrecoverable job failure after Json parse error?

Hello, When using FlinkKafkaConsumer011 with JSONKeyValueDeserializationSchema, if an invalid, non-parsable message is sent to the Kafka topic, the consumer expectedly fails with JsonParseException. So far so good, but this leads to the following loop: the job switches to FAILED then attempts to