[
https://issues.apache.org/jira/browse/NIFI-13543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880285#comment-17880285
]
ASF subversion and git services commented on NIFI-13543:
--------------------------------------------------------
Commit f106f8474a16edfd5cb97b41e4abceec1e144ffb in nifi's branch
refs/heads/support/nifi-1.x from Jim Steinebrey
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=f106f8474a ]
NIFI-13543 Backport HttpRecordSink service to NiFi 1.x
Signed-off-by: Pierre Villard <[email protected]>
This closes #9243.
> HTTPRecordSink
> --------------
>
> Key: NIFI-13543
> URL: https://issues.apache.org/jira/browse/NIFI-13543
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Jim Steinebrey
> Priority: Major
> Fix For: 2.0.0-M5
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The idea is to create an HTTPRecordSink that would make a POST request to a
> given HTTP endpoint for every record. The controller service would take in
> * URL endpoint
> * StandardWebClientServiceProvider
> * OAuth2 Access Token Provider
> * Record Writer
> * Max Batch Size
> The data that would be sent to the endpoint as the payload of the POST HTTP
> request would be the output of the writer. This is to allow potential format
> transformations that would be required to match the specifications of the
> target endpoint.
> It should also be possible to add dynamic properties that would be added as
> HTTP attributes including sensitive ones - similar to InvokeHTTP
> The potential use cases are:
> * Capturing bulletins via the QueryNiFiReportingTask and automatically
> filing Jira(s) for each bulletin (or similar systems PagerDuty, ServiceNow,
> etc)
> * Sending data with PutRecord processor and remove the need for splitting a
> flow file into many flow files made of a single record
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
