You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, realistically, most S3 users should want to use that setting. There's little real downside to it, it won't realistically impact performance, since S3 will now all be on sync IO with my recent bug fix (fluent/fluent-bit#6573).
2.0 is an opportunity to "break" backwards compatibility in small ways. While upstream already has 2.0 out, this distro has not released it yet (which will be our 3.0).
Our first release should include changing the default to on for Preserve_Data_Ordering
*If you have any comments or concerns on this plan, please note them in this issue.` This distro is still testing Fluent Bit 2.0 and so we will not release it until next year.
The text was updated successfully, but these errors were encountered:
Currently this field defaults to Off: https://docs.fluentbit.io/manual/pipeline/outputs/s3
However, realistically, most S3 users should want to use that setting. There's little real downside to it, it won't realistically impact performance, since S3 will now all be on sync IO with my recent bug fix (fluent/fluent-bit#6573).
2.0 is an opportunity to "break" backwards compatibility in small ways. While upstream already has 2.0 out, this distro has not released it yet (which will be our 3.0).
Our first release should include changing the default to
on
forPreserve_Data_Ordering
*If you have any comments or concerns on this plan, please note them in this issue.` This distro is still testing Fluent Bit 2.0 and so we will not release it until next year.
The text was updated successfully, but these errors were encountered: