-
Notifications
You must be signed in to change notification settings - Fork 897
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
Minor clarification on BatchExportingProcessor behavior #4164
Minor clarification on BatchExportingProcessor behavior #4164
Conversation
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.
That is a lot more readable and AFAIK it is indeed what the authors had in mind.
Co-authored-by: Tristan Sloughter <[email protected]>
@tsloughter Could you take another look to see if the wording looks good? |
Still need more reviews from @open-telemetry/technical-committee , could you help? |
@open-telemetry/technical-committee Please review/merge! Thanks. |
@open-telemetry/technical-committee @arminru Gentle reminder to look at this when you get a chance! |
…ry#4164) Co-authored-by: Tristan Sloughter <[email protected]> Co-authored-by: Armin Ruech <[email protected]>
Changes
I am unsure of the meaning of the current wording, so trying to clarify here. It looks like the current wording was intended to convey that export() should not be triggered until previous export() finished, even if the triggers (batch-size met etc.) are ready. But the current wording is confusing. I hope I interpreted it correctly and this fix address the confusing aspect. If not, happy to correct myself.
For non-trivial changes, follow the change proposal process.
CHANGELOG.md
file updated for non-trivial changesspec-compliance-matrix.md
updated if necessary