[
https://issues.apache.org/jira/browse/SUBMARINE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Szilard Nemeth updated SUBMARINE-51:
------------------------------------
Description:
We need to "normalize" exceptions of YAML / CLI parser errors: Only print short
texts (instead of stacktraces) when any issue happens.
Some requirements (copied from SUBMARINE-47, quoting [~sunilg]):
{quote}
In YamlParseException, mostly it is using super methods to print the cause.
Since submarine is CLI driven, how bulky these exceptions traces will look like
in console if any failure happens in parsing. Lets me try to cover some cases.
1. If file doesn't exist, a simple cleaner message in console is enough to
state that the file is not present or invalid file.
2. If file contents are empty or in not a parsable format, we should show some
more exception details.
3. Now coming to some parsing error due to some sections are not correctly
indented or wrongly given, will we show the line number in exception stating
that this line has some issues in parsing.?
{quote}
was:
We need to "normalize" exceptions of YAML / CLI parser errors: Only print short
texts (instead of stacktraces) when any issue happens
Some requirements (copied from SUBMARINE-47, quoting [~sunilg]):
In YamlParseException, mostly it is using super methods to print the cause.
Since submarine is CLI driven, how bulky these exceptions traces will look like
in console if any failure happens in parsing. Lets me try to cover some cases.
1. If file doesn't exist, a simple cleaner message in console is enough to
state that the file is not present or invalid file.
2. If file contents are empty or in not a parsable format, we should show some
more exception details.
3. Now coming to some parsing error due to some sections are not correctly
indented or wrongly given, will we show the line number in exception stating
that this line has some issues in parsing.?
> Print short error messages in case of configuration issues
> ----------------------------------------------------------
>
> Key: SUBMARINE-51
> URL: https://issues.apache.org/jira/browse/SUBMARINE-51
> Project: Hadoop Submarine
> Issue Type: Improvement
> Reporter: Szilard Nemeth
> Assignee: Szilard Nemeth
> Priority: Major
>
> We need to "normalize" exceptions of YAML / CLI parser errors: Only print
> short texts (instead of stacktraces) when any issue happens.
> Some requirements (copied from SUBMARINE-47, quoting [~sunilg]):
> {quote}
> In YamlParseException, mostly it is using super methods to print the cause.
> Since submarine is CLI driven, how bulky these exceptions traces will look
> like in console if any failure happens in parsing. Lets me try to cover some
> cases.
> 1. If file doesn't exist, a simple cleaner message in console is enough to
> state that the file is not present or invalid file.
> 2. If file contents are empty or in not a parsable format, we should show
> some more exception details.
> 3. Now coming to some parsing error due to some sections are not correctly
> indented or wrongly given, will we show the line number in exception stating
> that this line has some issues in parsing.?
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
