[
https://issues.apache.org/jira/browse/NIFI-7482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17114324#comment-17114324
]
ASF subversion and git services commented on NIFI-7482:
-------------------------------------------------------
Commit 97a919a3be37c8e78b623ffacf9b1f22db534644 in nifi's branch
refs/heads/master from Andy LoPresto
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=97a919a ]
NIFI-7482 Changed InvokeHTTP to be extensible.
Added unit test.
This closes #4291.
Signed-off-by: Arpad Boda <ab...@apache.org>
> 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: 20m
> 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)
