You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Nico Kruber (JIRA)" <ji...@apache.org> on 2017/01/20 14:16:26 UTC
[jira] [Created] (FLINK-5591) queryable state: request failures
failing on the server side do not contain client stack trace
Nico Kruber created FLINK-5591:
----------------------------------
Summary: queryable state: request failures failing on the server side do not contain client stack trace
Key: FLINK-5591
URL: https://issues.apache.org/jira/browse/FLINK-5591
Project: Flink
Issue Type: Improvement
Components: Queryable State
Affects Versions: 1.2.0
Reporter: Nico Kruber
Assignee: Nico Kruber
Failures during queries using QueryableStateClient throw exceptions like UnknownKeyOrNamespace but these are thrown on the server side with its stacktrace included, then serialised and sent over to the client where they are deserialised and re-thrown.
For debugging it would help a lot if these "server-exceptions" would be encapsulated in new client-exception instances so that we also get the client's stack trace. Especially since failing requests may be caused by the client itself, e.g. non-existing jobs/keys, wrong namespace/serialisers, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)