You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Andy LoPresto (Jira)" <ji...@apache.org> on 2020/05/22 17:59:00 UTC
[jira] [Updated] (NIFI-7482) InvokeHTTP should not be final
[ https://issues.apache.org/jira/browse/NIFI-7482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy LoPresto updated NIFI-7482:
--------------------------------
Status: Patch Available (was: In Progress)
> InvokeHTTP should not be final
> ------------------------------
>
> Key: NIFI-7482
> URL: https://issues.apache.org/jira/browse/NIFI-7482
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.11.4
> Reporter: Andy LoPresto
> Assignee: Andy LoPresto
> Priority: Major
> Labels: InvokeHTTP, custom_processor, extension
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)