Uploaded image for project: 'Apache NiFi'
  1. Apache NiFi
  2. NIFI-7482

InvokeHTTP should not be final

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    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.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            alopresto Andy LoPresto
            alopresto Andy LoPresto
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 0.5h
                0.5h

                Slack

                  Issue deployment