[
https://issues.apache.org/jira/browse/OOZIE-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13512065#comment-13512065
]
Virag Kothari commented on OOZIE-1101:
--------------------------------------
Good work..
Only comment is there are some places where two parameters are passed in
Exception while the error code only accepts one
E.g
{code}
throw new CommandException(ErrorCode.E0902, e.getMessage(), e);
{code}
While the ErrorCode accepts only 1 parameter
{code}
E0902(XLog.OPS, "Exception occured: [{0}]"),
{code}
> Fix log messages that contain {0} or similar
> --------------------------------------------
>
> Key: OOZIE-1101
> URL: https://issues.apache.org/jira/browse/OOZIE-1101
> Project: Oozie
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-1101.patch, OOZIE-1101.patch, OOZIE-1101.patch,
> OOZIE-1101.patch
>
>
> Working on various parts of Oozie and looking at the logs, I've noticed on
> multiple occasions that the {0}, {1}, etc are sometimes still in the log
> messages. We should go through all occurrences of {0} and verify/fix them.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
