[NIFI-4590] customValidate() fails during unit tests when isExpressionLanguagePresent() is called

• Type: Test
• Status: Resolved
• Priority: Major
• Resolution: Implemented
• Component/s: Core Framework
• Assignee: Unassigned
• Reporter: Matt Burgess
• Created: 09/Nov/17 15:00
• Updated: 09/Oct/23 17:36
• Resolved: 09/Oct/23 17:36

Description

When isExpressionLanguagePresent() is called from a customValidate() method in a processor during a unit test, a NullPointerException is thrown.

Inside that method in MockPropertyValue, a Boolean (not boolean) reference "expectExpressions" appears that expectExpressions has not yet been populated by the time isExpressionLanguagePresent() is called, and the if(!expectExpressions) clause results in an NPE.

Not sure if the fix is to change expectExpressions to be a boolean, or to allow for expectExpressions == null in isExpressionLanguagePresent(), or some third option to achieve the desired behavior while maintaining an accurate mock of true behavior.

Issue Links

• is fixed by: NIFI-4717 Minor bugs and performance improvements to record-oriented processors
• is fixed by: NIFI-6318 Support EL in CSV formatting properties