[
https://issues.apache.org/jira/browse/NIFI-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-5827.
----------------------------------
Resolution: Feedback Received
Apache NiFi 1.x is no longer maintained and no new release is planned on the
1.x release line. Marking as resolved as part of a cleanup operation. Please
open a new one with an updated description if this is still relevant for NiFi
2.x.
> CaptureChangeMySQL fails when table has been drop before log processing
> -----------------------------------------------------------------------
>
> Key: NIFI-5827
> URL: https://issues.apache.org/jira/browse/NIFI-5827
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.8.0
> Environment: MySQL 5.7.16
> Reporter: Fabien Sarcel
> Priority: Major
> Attachments: nifi-app.log
>
>
> If I create a MySQL table, then drop it and launch a new flow with a
> CaptureChangeMySQL processor using the "Distributed Map Cache Client"
> parameter, the flow is running into an error.
> I think CaptureChangeMySQL is executing "loadTableInfo" function for a table
> that is not in the database anymore and this creates a NiFi error.
> But the worst is that after this error the flow loses database connection and
> keep going create new connections that can disturb MySQL database.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
