[
https://issues.apache.org/jira/browse/NIFI-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16235362#comment-16235362
]
ASF subversion and git services commented on NIFI-4490:
-------------------------------------------------------
Commit 64133379188eabbb672f695b2ab9c168f49c10b4 in nifi's branch
refs/heads/master from [~ijokarumawak]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=6413337 ]
NIFI-4490: Ensure driver settings are correct before connecting binlog
Signed-off-by: Pierre Villard <[email protected]>
This closes #2244.
> Repetitive events detected on changing the incorrect driver name in
> CaptureChangeMySQL
> --------------------------------------------------------------------------------------
>
> Key: NIFI-4490
> URL: https://issues.apache.org/jira/browse/NIFI-4490
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Matt Burgess
> Assignee: Koji Kawamura
> Priority: Major
>
> Followed the below steps
> 1. In CaptureChangeMySQL, set the driver name to "com.mysql.some.driver"
> 2. Create a table in the test database and start the CaptureChangeMySQL
> processor
> 3. "Error creating binlog enrichment JDBC connection" error message is thrown
> which is correct.
> This completes the first test. Next do the following
> 1. Correct the driver name
> 2. Reset the binlog events by running "RESET MASTER"
> 3. Clear the state of the CaptureChangeMySQL processor.
> 4. Start the CaptureChangeMySQL processor.
> Result : The Create statement which was triggered when the driver was invalid
> is detected thrice in the tests that I carried out by CaptureChangeMySQL
> processor
> Expected : The event should not have been detected at all since the binlogs
> have been deleted, state reset and the database pattern hardcoded to a single
> db
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
