[NIFI-4629] Non-existing attribute in ControlRate configuration causes NullPointerException

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.4.0
• Fix Version/s: 1.5.0
• Component/s: Configuration, Core UI
• Labels: ControlRate NullPointerException Processor
• Environment: Ubuntu LTS 16.04 ; openjdk-8-jre
• Assignee: Unassigned
• Reporter: Fredrik Skolmli
• Created: 21/Nov/17 19:13
• Updated: 15/Dec/17 16:29
• Resolved: 15/Dec/17 15:37

Description

When using the ControlRate processor, defining the "Grouping Attribute" with a missing/non-existing attribute name produces NullPointerException errors.

Processor configuration:

Rate Control Criteria: flowfile count
Maximum rate: 10
Rate Controlled Attributes: (No value set)
Time Duration: 1 min
Grouping Attribute: foobar

ControlRate with the following configuration when sent a flowfile without the attribute foobar generates the following error:

ControlRate[id=dff05b32-015f-1000-db55-5957a9298bab] ControlRate[id=dff05b32-015f-1000-db55-5957a9298bab] failed to process due to java.lang.NullPointerException; rolling back session: null

Additionally, the incoming flowfiles now ends up in some "dead" state where I'm unable to even empty the queue.

A simple template for reproduction is attached.

Issue Links

• links to: GitHub Pull Request #2345