[NIFI-7482] InvokeHTTP should not be final

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.11.4
• Fix Version/s: 1.12.0
• Component/s: Extensions
• Labels: InvokeHTTP custom_processor extension
• Assignee: Andy LoPresto
• Reporter: Andy LoPresto
• Created: 22/May/20 17:46
• Updated: 19/Oct/21 00:20
• Resolved: 22/May/20 18:46

Description

The InvokeHTTP processor is defined as final, which means custom processors cannot extend it. I see no reason this class should be final, as other standard processors are not defined as such with no visible problems. InvokeHTTP is a processor that users frequently want to modify, and allowing custom extensions is much easier than duplicating all native behavior in a new processor.

Issue Links

• is duplicated by: NIFI-9296 Improve the code structure of the InvokeHTTP processor
• is related to: NIFI-9015 Ability to derive custom Rest API processes from InvokeHTTP
• links to: GitHub Pull Request #4291