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]
mentioned 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:
.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
OK, thanks a lot Fabian.
Adrian
- Original message -From: Fabian Hueske To: Adrian Vasiliu Cc: user Subject: Re: ElasticsearchSink in Flink 1.4.0 with Elasticsearch 5.2+Date: Mon, Jan 22, 2018 2:54 PM
Hi Adrian, thanks for raising this issue again.I agree, we should add support for
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: org.elasticsearch.action.bulk.
to implement custom handling is okay...
Thanks
Adrian
- Original message -From: Nico Kruber To: Adrian Vasiliu Cc: user@flink.apache.orgSubject: Re: Unrecoverable job failure after Json parse error?Date: Tue, Jan 16, 2018 3:18 PM
Nice, I didn't even read that far myself :P-> turns
improvement 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 To: Adrian Vasiliu , user@flink.apache.orgCc:Subject: Re: Unrecoverable job failure after Json parse error?Date: Tu
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 re