You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Fabien Sarcel (JIRA)" <ji...@apache.org> on 2018/11/16 11:58:00 UTC

[jira] [Created] (NIFI-5827) CaptureChangeMySQL fails when table has been drop before log processing

Fabien Sarcel created NIFI-5827:
-----------------------------------

             Summary: 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
         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
(v7.6.3#76005)