-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix aggregate processor local mode #4529
Conversation
Signed-off-by: Krishna Kondaka <[email protected]>
* | ||
* @return true if the event should be processed locally only | ||
*/ | ||
default boolean isForLocalProcessingOnly(Event event) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we use the existing isApplicableEventForPeerForwarding
?
Put another way, do we desire to support isApplicableEventForPeerForwarding=false and isForLocalProcessingOnly=false? This would always skip.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. If both are false, it would skip
Signed-off-by: Krishna Kondaka <[email protected]>
Signed-off-by: Krishna Kondaka <[email protected]>
Thanks Krishna! I appreciate you! |
Description
Local mode option added to aggregate processor in PR #4306 has a bug that when local mode is turned on the events are not passed to the remote peer but also skipped from passing it to the local inner processor. This change fixes the issue so that local mode works as expected.
Issues Resolved
Resolves #
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.