tached).
>
>
> From: Robert Metzger <rmetz...@apache.org>
> Date: Friday, March 10, 2017 at 1:18 PM
> To: "user@flink.apache.org" <user@flink.apache.org>
> Subject: Re: AWS exception serialization problem
>
> Can one of you guys provide us with a minimal exam
:18 PM
To: "user@flink.apache.org" <user@flink.apache.org>
Subject: Re: AWS exception serialization problem
Can one of you guys provide us with a minimal example to reproduce the issue?
(Ideally locally, not using EMR?)
I think once we can reproduce the issue its easy to fix.
On Thu,
ya go (see attached).
From: Robert Metzger <rmetz...@apache.org>
Date: Friday, March 10, 2017 at 1:18 PM
To: "user@flink.apache.org" <user@flink.apache.org>
Subject: Re: AWS exception serialization problem
Can one of you guys provide us with a minimal example to reproduc
Can one of you guys provide us with a minimal example to reproduce the
issue? (Ideally locally, not using EMR?)
I think once we can reproduce the issue its easy to fix.
On Thu, Mar 9, 2017 at 1:24 AM, Bruno Aranda wrote:
> Hi Stephan, we are running Flink 1.2.0 on Yarn
Hi Stephan, we are running Flink 1.2.0 on Yarn (AWS EMR cluster)
On Wed, 8 Mar 2017, 21:41 Stephan Ewen, wrote:
> @Bruno: How are you running Flink? On yarn, standalone, mesos, docker?
>
> On Wed, Mar 8, 2017 at 2:13 PM, Bruno Aranda
> wrote:
>
> Hi,
>
@Bruno: How are you running Flink? On yarn, standalone, mesos, docker?
On Wed, Mar 8, 2017 at 2:13 PM, Bruno Aranda wrote:
> Hi,
>
> We have seen something similar in Flink 1.2. We have an operation that
> parses some JSON, and when it fails to parse it, we can see the
>
Hi,
We have seen something similar in Flink 1.2. We have an operation that
parses some JSON, and when it fails to parse it, we can see the
ClassNotFoundException for the relevant exception (in our case
JsResultException from the play-json library). The library is indeed in the
shaded JAR,
Hi Shannon,
Just to clarify:
From the error trace, it seems like that the messages fetched from Kafka are
serialized `AmazonS3Exception`s, and you’re emitting a stream of
`AmazonS3Exception` as records from FlinkKafkaConsumer?
Is this correct? If so, I think we should just make sure that the
> is there some shading logic involved in the dependencies, concerning the AWS
> libraries?
Not that I am aware of. The AWS code is included in the job's fat jar as-is.
bug in TrySerializer#copy? Or somewhere that Kryo is being
>> configured?
>>
>> Thanks,
>> Shannon
>>
>>
>> From: Shannon Carey <sca...@expedia.com>
>> Date: Monday, March 6, 2017 at 7:09 PM
>> To: "user@flink.apache.org" <u
y <sca...@expedia.com>
Date: Monday, March 6, 2017 at 7:09 PM
To: "user@flink.apache.org" <user@flink.apache.org>
Subject: Re: AWS exception serialization problem
This happened when running Flink with bin/run-local.sh I notice that there only
appears to be one Java process.
ing
> configured?
>
> Thanks,
> Shannon
>
>
> From: Shannon Carey <sca...@expedia.com>
> Date: Monday, March 6, 2017 at 7:09 PM
> To: "user@flink.apache.org" <user@flink.apache.org>
> Subject: Re: AWS exception serialization problem
>
> This ha
er@flink.apache.org>>
Subject: AWS exception serialization problem
Has anyone encountered this or know what might be causing it?
java.lang.RuntimeException: Could not forward element to next operator
at
org.apache.flink.streaming.runtime.tasks.OperatorChain$CopyingChain
Has anyone encountered this or know what might be causing it?
java.lang.RuntimeException: Could not forward element to next operator
at
org.apache.flink.streaming.runtime.tasks.OperatorChain$CopyingChainingOutput.collect(OperatorChain.java:394)
at
14 matches
Mail list logo