Issues

Select view

Select search mode

 
50 of 127

If a plugin throws an exception, the pipeline fails without logging the error

Fixed

Description

Currently, when a plugin throws an exception, say an IllegalArgumentException, then that bubbles all the way up and fails the mapper or reducer and with that the entire job. It is ok to fail the pipeline, but the error should be logged so that it appears in the pipeline logs.

This happens, for example, when a plugin attempts to set a non-nullable field to null. That is a common error that users should be able to find in the logs.

Currently, that exception is only visible in the YARN console.

Release Notes

None

Attachments

1
  • 13 May 2017, 01:41 AM

duplicates

Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Affects versions

Components

Fix versions

Priority

Created November 1, 2016 at 11:19 PM
Updated May 13, 2017 at 1:43 AM
Resolved May 13, 2017 at 1:43 AM

Activity

Show:

Deepak Wadhwani May 13, 2017 at 1:41 AM

Logs with forced Illegal Argument Exception after the fix for Jira: https://cdap.atlassian.net/browse/CDAP-11483#icft=CDAP-11483