[ 
https://issues.apache.org/jira/browse/NIFI-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17021292#comment-17021292
 ] 

Frank commented on NIFI-4239:
-----------------------------

[~gerdan] [~davy.machado]

We are currently interested in such solution as well as we would like to avoid 
using debezium. 

Would this CDC Connector be available in the public Nifi repo ? Actually I 
haven't been able to find the branch related to this development.

Could you share a pointer to it ? maybe to help testing and os ?

Thanks;

 

> Implement a CaptureChangePostgreSQL processor
> ---------------------------------------------
>
>                 Key: NIFI-4239
>                 URL: https://issues.apache.org/jira/browse/NIFI-4239
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Gerdan Santos
>            Assignee: Gerdan Santos
>            Priority: Major
>         Attachments: 2020-01-11_23-37-172.png, 2020-01-11_23-37-58.png
>
>   Original Estimate: 2,688h
>  Remaining Estimate: 2,688h
>
> Inspired on CaptureChangeMySQL, this processor can use one Streaming 
> Replication PostgreSQL Connection to allow access to their transactional logs 
> and such, in order for external clients to have a "change data capture" (CDC) 
> capability.
> The processor would include properties needed for PostgreSQL connectivity 
> PostgreSQL Streaming Replication. It would also need to keep a "sequence ID" 
> such that an EnforceOrder processor (NIFI-3414) for example could guarantee 
> the order of CDC events for use cases such as replication. 
> It will likely need State Management for that, and may need other facilities 
> such as a DistributedMapCache in order to keep information (column names and 
> types, e.g.) that enrich the raw CDC events.
> The processor would accept no incoming connections (it is a "get" or source 
> processor), would be intended to run on the primary node only as a single 
> threaded processor, and would generate a flow file for each operation 
> (INSERT, UPDATE, DELETE, e.g.) in one or some number of formats (JSON, e.g.).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to