markap14 opened a new pull request, #115:
URL: https://github.com/apache/nifi-api/pull/115

   <!-- SPDX-License-Identifier: Apache-2.0 -->
   
   # Summary
   
   [NIFI-16574](https://issues.apache.org/jira/browse/NIFI-16574)
   
   This adds the NiFi API changes for draining a Process Group, as proposed in 
[NIP-51](https://issues.apache.org/jira/browse/NIP-51).
   
   - Adds the `@OnDrainInitiated` and `@OnDrainCompleted` lifecycle 
annotations. Processors and Controller Services can use them to process their 
data more aggressively while their Process Group is being drained. For example, 
MergeContent can use a short Max Bin Age so that bins don't wait a long time 
for more data that will never arrive.
   - Adds `beginDrain()` and `endDrain()` default methods to 
`ProcessGroupLifecycle`.
   - Updates `AbstractConnector.drainFlowFiles` to use those methods, so that a 
Connector drains its flow the same way as a Process Group. The protected helper 
methods in `AbstractConnector` are unchanged.
   
   All changes are additive and backward compatible. The framework and UI work 
is tracked separately under 
[NIFI-16573](https://issues.apache.org/jira/browse/NIFI-16573).
   
   # 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
   


-- 
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]

Reply via email to