-
Notifications
You must be signed in to change notification settings - Fork 70
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
waitForBuffers handling in processing? #348
Comments
#378 , log error can be handled by config a result handler on |
@lust4life Thanks, so with your PR, this should be fixed, I suppose? Since you switched from 'rejected' as the default to 'accepted' as the default? |
these are two different things, if target not accept a message,this will result a log error message to registry's logErrorHandler. changing pipeline processing result (NoResult) to acceptable is for fire-forget. e.g. user log a message, goto a pipe which have a buffer sink, it will only push to target by batches. So at this logging time, this message are in pipe's buffer, not in target, but we assume that this logging result is success. |
The text was updated successfully, but these errors were encountered: