My bad, I was looking at the wrong code path. The linked issue isn't
helpful, as it only slightly extends the exception message.
You cannot get the stacktrace in 1.7.X nor in the current RC for 1.8.0 .
I've filed https://issues.apache.org/jira/browse/FLINK-11902 to change this.
The 1.8.0 RC j
Hey Chesnay,
Actually I was mistaken by stating that in the JobManager logs I got the
full stacktrace because I actually got the following there:
2019-03-13 11:55:13,906 ERROR
org.apache.flink.runtime.webmonitor.handlers.JarRunHandler- Exception
occurred in REST handler:
org.apache.flink.clien
Can you give me the stacktrace that is logged in the JobManager logs?
On 13.03.2019 10:57, Wouter Zorgdrager wrote:
Hi Chesnay,
Unfortunately this is not true when I run the Flink 1.7.2 docker
images. The response is still:
{
"errors": [
"org.apache.flink.client.program.ProgramInvocationE
Hi Chesnay,
Unfortunately this is not true when I run the Flink 1.7.2 docker images.
The response is still:
{
"errors": [
"org.apache.flink.client.program.ProgramInvocationException: The
main method caused an error."
]
}
Regards,
Wouter Zorgdrager
Op wo 13 mrt. 2019 om 10:42 schr
You should get the full stacktrace if you upgrade to 1.7.2 .
On 13.03.2019 09:55, Wouter Zorgdrager wrote:
Hey all!
I'm looking for some advice on the following; I'm working on an
abstraction on top of Apache Flink to 'pipeline' Flink applications
using Kafka. For deployment this means that a
