[
https://issues.apache.org/jira/browse/NIFI-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988177#comment-15988177
]
ASF subversion and git services commented on NIFI-3749:
-------------------------------------------------------
Commit aa4efb43ca5dc85b55bc39c180ca447f4e9e3e01 in nifi's branch
refs/heads/master from [~mattyb149]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=aa4efb4 ]
NIFI-3749: Added database filtering to DDL events in CaptureChangeMySQL
This closes #1708.
Signed-off-by: Koji Kawamura <[email protected]>
> 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
> Fix For: 1.2.0
>
>
> 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)
