[jira] [Updated] (NIFI-3413) Implement a CaptureChangeMySQL processor

["Matt Burgess (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Burgess updated NIFI-3413:
-------------------------------
    Summary: Implement a CaptureChangeMySQL processor  (was: Implement a GetChangeDataCapture processor)

> Implement a CaptureChangeMySQL processor
> ----------------------------------------
>
>                 Key: NIFI-3413
>                 URL: https://issues.apache.org/jira/browse/NIFI-3413
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>             Fix For: 1.2.0
>
>
> Database systems such as MySQL, Oracle, and SQL Server allow access to their transactional logs and such, in order for external clients to have a "change data capture" (CDC) capability. I propose a GetChangeDataCapture processor to enable this in NiFi.
> The processor would be configured with a DBCPConnectionPool controller service, as well as a Database Type property (similar to the one in QueryDatabaseTable) for database-specific handling. Additional properties might include the CDC table name, etc.  Additional database-specific properties could be handled using dynamic properties (and the documentation should reflect this).
> 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.). The flow files would be transferred in time order (to enable a replication solution, for example), perhaps with some auto-incrementing attribute to also indicate order if need be.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)