[FLINK-18159] Add support for trimming stack traces in user-facing components

• Type: New Feature
• Status: Open
• Priority: Not a Priority
• Resolution: Unresolved
• Component/s: Command Line Client, Runtime / REST
• Labels: auto-deprioritized-major auto-deprioritized-minor
• Assignee: Unassigned
• Reporter: Chesnay Schepler
• Created: 05/Jun/20 12:33
• Updated: 27/Nov/21 23:06

Description

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:

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'.

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, but the flags are missing.

Issue Links

• is related to: FLINK-17765 Verbose client error messages