nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre Villard (Jira)" <>
Subject [jira] [Updated] (NIFI-4239) Implement a CaptureChangePostgreSQL processor
Date Fri, 21 Feb 2020 19:57:00 GMT


Pierre Villard updated NIFI-4239:
    Status: Patch Available  (was: Reopened)

> Implement a CaptureChangePostgreSQL processor
> ---------------------------------------------
>                 Key: NIFI-4239
>                 URL:
>             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
>          Time Spent: 1h 10m
>  Remaining Estimate: 2,686h 50m
> 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

View raw message