[jira] [Commented] (NIFI-5232) HttpConnectionService controller service
[
https://issues.apache.org/jira/browse/NIFI-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583771#comment-17583771
]
David Handermann commented on NIFI-5232:
Thanks for following up on this [~mike.thomsen]! The {{nifi-scripting-nar}}
depends on {{{}nifi-standard-services-api-nar{}}}, so scripted components
should be able to leverage the new service with the
{{WebClientServiceProvider}} interface bundled as a standard Controller Service.
> HttpConnectionService controller service
>
>
> Key: NIFI-5232
> URL: https://issues.apache.org/jira/browse/NIFI-5232
> Project: Apache NiFi
> Issue Type: New Feature
>Reporter: Mike Thomsen
>Priority: Major
>
> The functionality of InvokeHttp and related processors should be copied over
> to a controller service that can do much the same thing. This controller
> service would be able to handle all of the common scenarios with HTTP
> connections from processors going forward.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-5232) HttpConnectionService controller service
[ https://issues.apache.org/jira/browse/NIFI-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580894#comment-17580894 ] David Handermann commented on NIFI-5232: https://github.com/apache/nifi/pull/6268 is the pull request for NIFI-10244, which contains the implementation, now merged into main. > HttpConnectionService controller service > > > Key: NIFI-5232 > URL: https://issues.apache.org/jira/browse/NIFI-5232 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Mike Thomsen >Priority: Major > > The functionality of InvokeHttp and related processors should be copied over > to a controller service that can do much the same thing. This controller > service would be able to handle all of the common scenarios with HTTP > connections from processors going forward. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-5232) HttpConnectionService controller service
[ https://issues.apache.org/jira/browse/NIFI-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580885#comment-17580885 ] Mike Thomsen commented on NIFI-5232: Sure. Got a link? > HttpConnectionService controller service > > > Key: NIFI-5232 > URL: https://issues.apache.org/jira/browse/NIFI-5232 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Mike Thomsen >Priority: Major > > The functionality of InvokeHttp and related processors should be copied over > to a controller service that can do much the same thing. This controller > service would be able to handle all of the common scenarios with HTTP > connections from processors going forward. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-5232) HttpConnectionService controller service
[
https://issues.apache.org/jira/browse/NIFI-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17580804#comment-17580804
]
David Handermann commented on NIFI-5232:
NIFI-10244 implemented something similar to the capabilities described in this
issue in a {{WebClientServiceProvider}} Controller Service and
{{WebClientService}} abstraction.
[~mike.thomsen] Perhaps this issue could be closed in light of that
implementation?
> HttpConnectionService controller service
>
>
> Key: NIFI-5232
> URL: https://issues.apache.org/jira/browse/NIFI-5232
> Project: Apache NiFi
> Issue Type: New Feature
>Reporter: Mike Thomsen
>Priority: Major
>
> The functionality of InvokeHttp and related processors should be copied over
> to a controller service that can do much the same thing. This controller
> service would be able to handle all of the common scenarios with HTTP
> connections from processors going forward.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-5232) HttpConnectionService controller service
[ https://issues.apache.org/jira/browse/NIFI-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16487336#comment-16487336 ] Mike Thomsen commented on NIFI-5232: I think it might be worthwhile to take this over to the developer list. > HttpConnectionService controller service > > > Key: NIFI-5232 > URL: https://issues.apache.org/jira/browse/NIFI-5232 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Mike Thomsen >Priority: Major > > The functionality of InvokeHttp and related processors should be copied over > to a controller service that can do much the same thing. This controller > service would be able to handle all of the common scenarios with HTTP > connections from processors going forward. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-5232) HttpConnectionService controller service
[ https://issues.apache.org/jira/browse/NIFI-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16487315#comment-16487315 ] Otto Fowler commented on NIFI-5232: --- The reason I ask: I have a PR out for an InvokeHTTP for aws gateway api services. Part of why this concept occurred to me is the amount of replication I had to do there. I am wondering how this could be factored such that we have as much shared and common as possible. I *think* that an http execution service or service interface could be factored such that a client could use http or aws or whatever without knowing or caring, esp as it relates to records. > HttpConnectionService controller service > > > Key: NIFI-5232 > URL: https://issues.apache.org/jira/browse/NIFI-5232 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Mike Thomsen >Priority: Major > > The functionality of InvokeHttp and related processors should be copied over > to a controller service that can do much the same thing. This controller > service would be able to handle all of the common scenarios with HTTP > connections from processors going forward. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-5232) HttpConnectionService controller service
[ https://issues.apache.org/jira/browse/NIFI-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16487300#comment-16487300 ] Otto Fowler commented on NIFI-5232: --- [~mike.thomsen] just to clarify, do we want something that builds and provides http clients, or something that executes requests? > HttpConnectionService controller service > > > Key: NIFI-5232 > URL: https://issues.apache.org/jira/browse/NIFI-5232 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Mike Thomsen >Priority: Major > > The functionality of InvokeHttp and related processors should be copied over > to a controller service that can do much the same thing. This controller > service would be able to handle all of the common scenarios with HTTP > connections from processors going forward. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-5232) HttpConnectionService controller service
[ https://issues.apache.org/jira/browse/NIFI-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16487285#comment-16487285 ] Mike Thomsen commented on NIFI-5232: [~ottobackwards] feel free to edit this and add your thoughts. > HttpConnectionService controller service > > > Key: NIFI-5232 > URL: https://issues.apache.org/jira/browse/NIFI-5232 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Mike Thomsen >Priority: Major > > The functionality of InvokeHttp and related processors should be copied over > to a controller service that can do much the same thing. This controller > service would be able to handle all of the common scenarios with HTTP > connections from processors going forward. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
