lordgamez commented on PR #1616: URL: https://github.com/apache/nifi-minifi-cpp/pull/1616#issuecomment-1660008176
Some overview of the inner workings of MergeContent: - Resurrect flow file is the process of restoring the unprocessed flow files from the flow file repository after restart. This is done for each processor and in case of the MergeContent this also means restoring flow files previously stored in the internal Self relationship. After restoring these flow files they also have to be sorted into their respective bins to restore the same bin state as before the restart. - Batches and batch size represent the maximum number of flow files to be processed from the incoming relationship. - A bin represents a set of flow files that belong together defined by the processor properties. In MergeContent correlated flow files are defined by the `CorrelationAttributeName` property which defines the attribute that provides the `groupid` for the bin the flow file belongs to. - When a bin reaches a limit defined by the maximum age or the maximum size, the bin becomes ready, and ready bins can be merged. - Preprocess flow file only checks for deprecated attributes and sets the value of the deprecated attribute to the value of the new renamed attribute. - Groups are set of bins with the same groupid. It can happen that a bin cannot accept a new flow files because it would go above its size limit for example, so a new bin is created with this new flow file and added to the same group of bins. - I think bundle is just a synonym for bin in the user descriptions. It is more understandable from a user's perspective than bin. - Entry is a member flow file of a bin -- 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]
