You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matt Burgess (Jira)" <ji...@apache.org> on 2020/01/21 22:49:00 UTC
[jira] [Assigned] (NIFI-7054) Add RecordSinkServiceLookup
[ https://issues.apache.org/jira/browse/NIFI-7054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Burgess reassigned NIFI-7054:
----------------------------------
Assignee: Matt Burgess
> Add RecordSinkServiceLookup
> ---------------------------
>
> Key: NIFI-7054
> URL: https://issues.apache.org/jira/browse/NIFI-7054
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
>
> The RecordSinkService controller service interface was added in NiFi 1.10 (via NIFI-6780) to decouple the destination for records in a FlowFile from the format of those records. Since then there have been various implementations (NIFI-6799, NIFI-6819). Other controller services have been augmented with a "lookup" pattern where the actual CS can be swapped out during the flow based on an attribute/variable (such as DBCPConnectionPoolLookup).
> RecordSinkService could be improved to have such a lookup as well, especially with the advent of the PutRecord processor (NIFI-6947). This would allow some flow files to be routed to Kafka while others are sent Site-to-Site for example, all with a single configured controller service.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)