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 2017/04/27 14:35:04 UTC

[jira] [Updated] (NIFI-3749) CaptureChangeMySQL should filter Query and XID events by database regex

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

Matt Burgess updated NIFI-3749:
-------------------------------
    Status: Patch Available  (was: In Progress)

> CaptureChangeMySQL should filter Query and XID events by database regex
> -----------------------------------------------------------------------
>
>                 Key: NIFI-3749
>                 URL: https://issues.apache.org/jira/browse/NIFI-3749
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.2.0
>            Reporter: Koji Kawamura
>            Assignee: Matt Burgess
>
> Although Query events including BEGIN/COMMIT and DDL statements do not have corresponding TableMap event, they still have 'database' name. So, it's possible to apply 'database' filter regex to filter out unnecessary events.
> Currently, Queries executed against a database which is not in interest can generate FlowFiles, and it can cause unexpected behavior.
> When we fix this, we should be careful about XID event and 'inTransaction' flag as XID event only has transaction id, we may need to add checking 'skipTable', too.
> Also, we need to pass database to DDLEventInfo.tableInfo to write database name into outgoing FlowFile.
> Finally, Begin/CommitTransactionEventInfo currently don't have database property or TableInfo in it. Adding database property to these class might be a right approach.



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