[
https://issues.apache.org/jira/browse/FLINK-18159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-18159:
-----------------------------------
Labels: auto-deprioritized-major (was: stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 ago and has not received any updates so
it is being deprioritized. If this ticket is actually Major, please raise the
priority and ask a committer to assign you the issue or revive the public
discussion.
> Add support for trimming stack traces in user-facing components
> ---------------------------------------------------------------
>
> Key: FLINK-18159
> URL: https://issues.apache.org/jira/browse/FLINK-18159
> Project: Flink
> Issue Type: New Feature
> Components: Command Line Client, Runtime / REST
> Reporter: Chesnay Schepler
> Priority: Minor
> Labels: auto-deprioritized-major
>
> Add a verbosity query parameter / flag(==config option) into the REST API /
> CLI to trim the exception stack traces, which means excluding the location
> information.
> The result would be something like this:
> {code}
> org.apache.flink.runtime.client.JobSubmissionException: Failed to submit job.
> Caused by: java.lang.RuntimeException:
> org.apache.flink.runtime.client.JobExecutionException: Could not set up
> JobManager
> Caused by: org.apache.flink.runtime.client.JobExecutionException: Could not
> set up JobManager
> Caused by: java.io.FileNotFoundException: Cannot find checkpoint or savepoint
> file/directory 'ashudasd' on file system 'file'.
> {code}
> This approach renders even the biggest stack traces fairly readable, and is
> rather convenient since it only requires changes in the actual user-facing
> components.
> Logging would not be impacted by this.
> The trimming was already implemented in this
> [PR|https://github.com/apache/flink/pull/12392], but the flags are missing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
