[jira] [Updated] (FLINK-12781) run job REST api doesn't return complete stack trace for start job failure
[
https://issues.apache.org/jira/browse/FLINK-12781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Zhen Wu updated FLINK-12781:
---
Description:
We use REST api to start a job in Flink cluster.
https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html#jars-jarid-run
When there is exception during job construction, the response payload doesn't
contain the full stack trace.
{code}
{"errors":["org.apache.flink.client.program.ProgramInvocationException: The
main method caused an error."]}
{code}
This problem becomes more serious after FLINK-11134 got released in 1.7.2,
because stack trace is completely lost now. FLINK-11134 is doing the right
thing. We just need the response payload to contain the full stack trace, which
seems to have been an issue/fix since 1.5. we know 1.4 doesn't have this issue
and correctly return full stack trace
on the jobmanager log, we only get
{code}
2019-06-07 17:42:40,136 ERROR
org.apache.flink.runtime.webmonitor.handlers.JarRunHandler- Exception
occurred in REST handler:
org.apache.flink.client.program.ProgramInvocationException: The main method
caused an error.
{code}
was:
We use REST api to start a job in Flink cluster.
https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html#jars-jarid-run
When there is exception during job construction, the response payload doesn't
contain the full stack trace.
{code}
{"errors":["org.apache.flink.client.program.ProgramInvocationException: The
main method caused an error."]}
{code}
This problem becomes more serious after FLINK-11134 got released in 1.7.2,
because stack trace is completely lost now. FLINK-11134 is doing the right
thing. We just need the response payload to contain the full stack trace, which
seems to have been an issue/fix since 1.5. we know 1.4 doesn't have this issue
and correctly return full stack trace
> run job REST api doesn't return complete stack trace for start job failure
> --
>
> Key: FLINK-12781
> URL: https://issues.apache.org/jira/browse/FLINK-12781
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / REST
>Reporter: Steven Zhen Wu
>Priority: Major
>
> We use REST api to start a job in Flink cluster.
> https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html#jars-jarid-run
> When there is exception during job construction, the response payload doesn't
> contain the full stack trace.
> {code}
> {"errors":["org.apache.flink.client.program.ProgramInvocationException: The
> main method caused an error."]}
> {code}
> This problem becomes more serious after FLINK-11134 got released in 1.7.2,
> because stack trace is completely lost now. FLINK-11134 is doing the right
> thing. We just need the response payload to contain the full stack trace,
> which seems to have been an issue/fix since 1.5. we know 1.4 doesn't have
> this issue and correctly return full stack trace
> on the jobmanager log, we only get
> {code}
> 2019-06-07 17:42:40,136 ERROR
> org.apache.flink.runtime.webmonitor.handlers.JarRunHandler- Exception
> occurred in REST handler:
> org.apache.flink.client.program.ProgramInvocationException: The main method
> caused an error.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FLINK-12781) run job REST api doesn't return complete stack trace for start job failure
[
https://issues.apache.org/jira/browse/FLINK-12781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Zhen Wu updated FLINK-12781:
---
Description:
We use REST api to start a job in Flink cluster.
https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html#jars-jarid-run
When there is exception during job construction, the response payload doesn't
contain the full stack trace.
{code}
{"errors":["org.apache.flink.client.program.ProgramInvocationException: The
main method caused an error."]}
{code}
This problem becomes more serious after FLINK-11134 got released in 1.7.2,
because stack trace is completely lost now. FLINK-11134 is doing the right
thing. We just need the response payload to contain the full stack trace, which
seems to have been an issue/fix since 1.5. we know 1.4 doesn't have this issue
and correctly return full stack trace
was:
We use REST api to start a job in Flink cluster.
https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html#jars-jarid-run
When there is exception during job construction, the response payload doesn't
contain the full stack trace.
{code}
{"errors":["org.apache.flink.client.program.ProgramInvocationException: The
main method caused an error."]}
{code}
This problem becomes more serious after FLINK-11134 got released in 1.7.2,
because stack trace is completely lost now. FLINK-11134 is doing the right
thing. We just need the response payload to contain the full stack trace, which
has always been an issue/fix.
> run job REST api doesn't return complete stack trace for start job failure
> --
>
> Key: FLINK-12781
> URL: https://issues.apache.org/jira/browse/FLINK-12781
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / REST
>Reporter: Steven Zhen Wu
>Priority: Major
>
> We use REST api to start a job in Flink cluster.
> https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html#jars-jarid-run
> When there is exception during job construction, the response payload doesn't
> contain the full stack trace.
> {code}
> {"errors":["org.apache.flink.client.program.ProgramInvocationException: The
> main method caused an error."]}
> {code}
> This problem becomes more serious after FLINK-11134 got released in 1.7.2,
> because stack trace is completely lost now. FLINK-11134 is doing the right
> thing. We just need the response payload to contain the full stack trace,
> which seems to have been an issue/fix since 1.5. we know 1.4 doesn't have
> this issue and correctly return full stack trace
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FLINK-12781) run job REST api doesn't return complete stack trace for start job failure
[
https://issues.apache.org/jira/browse/FLINK-12781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Zhen Wu updated FLINK-12781:
---
Description:
We use REST api to start a job in Flink cluster.
https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html#jars-jarid-run
When there is exception during job construction, the response payload doesn't
contain the full stack trace.
{code}
{"errors":["org.apache.flink.client.program.ProgramInvocationException: The
main method caused an error."]}
{code}
This problem becomes more serious after FLINK-11134 got released in 1.7.2,
because stack trace is completely lost now. FLINK-11134 is doing the right
thing. We just need the response payload to contain the full stack trace, which
has always been an issue/fix.
was:
We use REST api to start a job in Flink cluster.
https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html#jars-jarid-run
When there is exception during job construction, the response payload doesn't
contain the full stack trace.
{code}
{"errors":["org.apache.flink.client.program.ProgramInvocationException: The
main method caused an error."]}
{code}
This problem becomes more serious after FLINK-11134 got released in 1.7.2,
because stack trace is completely lost now. FLINK-11134 is doing the right
thing. But we need the response payload to contain the full stack trace.
> run job REST api doesn't return complete stack trace for start job failure
> --
>
> Key: FLINK-12781
> URL: https://issues.apache.org/jira/browse/FLINK-12781
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / REST
>Reporter: Steven Zhen Wu
>Priority: Major
>
> We use REST api to start a job in Flink cluster.
> https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html#jars-jarid-run
> When there is exception during job construction, the response payload doesn't
> contain the full stack trace.
> {code}
> {"errors":["org.apache.flink.client.program.ProgramInvocationException: The
> main method caused an error."]}
> {code}
> This problem becomes more serious after FLINK-11134 got released in 1.7.2,
> because stack trace is completely lost now. FLINK-11134 is doing the right
> thing. We just need the response payload to contain the full stack trace,
> which has always been an issue/fix.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FLINK-12781) run job REST api doesn't return complete stack trace for start job failure
[
https://issues.apache.org/jira/browse/FLINK-12781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Zhen Wu updated FLINK-12781:
---
Description:
We use REST api to start a job in Flink cluster.
[https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html#jars-jarid-run]
When there is exception during job construction, the response payload doesn't
contain the full stack trace.
{code}
{"errors":["org.apache.flink.client.program.ProgramInvocationException: The
main method caused an error."]}
{code}
This problem becomes more serious after FLINK-11134 got released in 1.7.2,
because stack trace is completely lost now. FLINK-11134 is doing the right
thing. But we need the response payload to contain the full stack trace.
was:
We use REST api to start a job in Flink cluster.
[https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html#jars-jarid-run]
When there is exception during job construction, the response payload doesn't
contain the full stack trace.
```
{"errors":["org.apache.flink.client.program.ProgramInvocationException: The
main method caused an error."]}
```
This problem becomes more serious after FLINK-11134 got released in 1.7.2,
because stack trace is completely lost now. FLINK-11134 is doing the right
thing. But we need the response payload to contain the full stack trace.
> run job REST api doesn't return complete stack trace for start job failure
> --
>
> Key: FLINK-12781
> URL: https://issues.apache.org/jira/browse/FLINK-12781
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / REST
>Reporter: Steven Zhen Wu
>Priority: Major
>
> We use REST api to start a job in Flink cluster.
> [https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html#jars-jarid-run]
>
>
> When there is exception during job construction, the response payload doesn't
> contain the full stack trace.
> {code}
> {"errors":["org.apache.flink.client.program.ProgramInvocationException: The
> main method caused an error."]}
> {code}
> This problem becomes more serious after FLINK-11134 got released in 1.7.2,
> because stack trace is completely lost now. FLINK-11134 is doing the right
> thing. But we need the response payload to contain the full stack trace.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FLINK-12781) run job REST api doesn't return complete stack trace for start job failure
[
https://issues.apache.org/jira/browse/FLINK-12781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Zhen Wu updated FLINK-12781:
---
Description:
We use REST api to start a job in Flink cluster.
https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html#jars-jarid-run
When there is exception during job construction, the response payload doesn't
contain the full stack trace.
{code}
{"errors":["org.apache.flink.client.program.ProgramInvocationException: The
main method caused an error."]}
{code}
This problem becomes more serious after FLINK-11134 got released in 1.7.2,
because stack trace is completely lost now. FLINK-11134 is doing the right
thing. But we need the response payload to contain the full stack trace.
was:
We use REST api to start a job in Flink cluster.
[https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html#jars-jarid-run]
When there is exception during job construction, the response payload doesn't
contain the full stack trace.
{code}
{"errors":["org.apache.flink.client.program.ProgramInvocationException: The
main method caused an error."]}
{code}
This problem becomes more serious after FLINK-11134 got released in 1.7.2,
because stack trace is completely lost now. FLINK-11134 is doing the right
thing. But we need the response payload to contain the full stack trace.
> run job REST api doesn't return complete stack trace for start job failure
> --
>
> Key: FLINK-12781
> URL: https://issues.apache.org/jira/browse/FLINK-12781
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / REST
>Reporter: Steven Zhen Wu
>Priority: Major
>
> We use REST api to start a job in Flink cluster.
> https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html#jars-jarid-run
> When there is exception during job construction, the response payload doesn't
> contain the full stack trace.
> {code}
> {"errors":["org.apache.flink.client.program.ProgramInvocationException: The
> main method caused an error."]}
> {code}
> This problem becomes more serious after FLINK-11134 got released in 1.7.2,
> because stack trace is completely lost now. FLINK-11134 is doing the right
> thing. But we need the response payload to contain the full stack trace.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
