Pierre Villard created NIFI-4344:
------------------------------------
Summary: Improve bulletin messaging with exception details
Key: NIFI-4344
URL: https://issues.apache.org/jira/browse/NIFI-4344
Project: Apache NiFi
Issue Type: Improvement
Components: Core Framework, Core UI
Reporter: Pierre Villard
In some environments it is not possible/allowed to access the NiFi nodes (and
consequently the log files). In such a situation, when developing a workflow,
the only option to understand what could be wrong with a processor is to look
at the bulletins.
However, the bulletins only contain the message of the main exception. Quite
often, the very useful messages to understand what is going on are located into
the wrapped exception. At the moment, the only option is to go into the log
files to get the messages. Even when access to the log files is authorized this
can unnecessarily slow down workflow development.
Ideally the full exception should be stored with the bulletin. However granting
access to a full stack trace can raise security concerns, and besides, the
bulletin tooltips are not designed to display large amount of data.
Additional data would be provided in the bulletins view only. Few options are
available:
- display the full stack trace in the bulletins view but only for users with
restricted component authorization.
- display an enriched message with the concatenation of the detailed messages
of the stack trace in the bulletins view (with or without restriction).
Adding an example to illustrate the problem: with ConvertRecord, in case
something is wrong with the schemas for the input/output data, the error is
handled with:
{code:title=ConvertRecord.java|borderStyle=solid}
} catch (final SchemaNotFoundException | MalformedRecordException e) {
throw new ProcessException("Could not parse incoming data", e);
}
{code}
In this case the bulletin will contain very little information.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
