mattyb149 opened a new pull request, #6907: URL: https://github.com/apache/nifi/pull/6907
# Summary [NIFI-11094](https://issues.apache.org/jira/browse/NIFI-11094) This PR refactors CaptureChangeMySQL to support two modes of operation, N events per FlowFile and one transaction per FlowFile. The default is N events per FlowFile with N set to 1 to retain existing behavior (1 event per FlowFile). However now this number is configurable, or the user can choose to output a FlowFile with all events between BEGIN and COMMIT events. The latter can help with downstream processing, as PutDatabaseRecord treats a FlowFile as a transaction so failure handling can be more consistent. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [x] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [x] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-00000` - [x] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-00000` ### Pull Request Formatting - [x] Pull Request based on current revision of the `main` branch - [x] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 8 - [x] JDK 11 - [ ] JDK 17 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [x] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
