Reading WorkFlowNodeStateDetail from MDS may throw NPE
Description
Release Notes
Fixes an issue with retrieving workflow state if it contains an exception without a message.
Activity
Show:
Ali Anwar July 25, 2017 at 11:59 PM
Without this fix, the following error can be seen in the master logs repeatedly (I see it twice every second):
Andreas Neumann June 5, 2017 at 8:51 PMEdited
PR against 4.2: https://github.com/caskdata/cdap/pull/9024
PR against 4.1: https://github.com/caskdata/cdap/pull/9049
Andreas Neumann June 5, 2017 at 5:18 PM
This is fixed in 4.2. Will send a PR for back-port to 4.1
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Created June 2, 2017 at 9:25 PM
Updated July 25, 2017 at 11:59 PM
Resolved June 5, 2017 at 8:53 PM
The WorkflowNodeStateDetail contains an optional Throwable in case the node failed. When reading this back from the store, we use BasicThrowableCodec, which fails with NPE if the throwable does not have a message. For example, an NPE does not have a message.
The issue is that jsonObj.get("message") may be null if the original Throwable did not have a message.