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
Is your feature request related to a problem? Please describe.
From my current understanding, log file is visible after a timekey interval or a buffer size.
If we configure with short time range there should have many files generated in case log content itself is not big.
If we configure with large time range then we need wait quite some time for log visibility.
Describe the solution you'd like
S3 support append semantic, so maybe we can implement with append file instead of put semantic.
Describe alternatives you've considered
File/WebHdfs plugin seems support append files.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Thanks for your request.
I don't know why the current out_s3 plugin doesn't support the append feature.
If anyone knows any reason, please let me know.
You mean that if we want to make a large file unit, we have to keep it in the buffer for a long period of time, and it is inconvenient, right?
If you have any sample implementations, I would appreciate it if you could share them.
Or PRs are welcome!
Is your feature request related to a problem? Please describe.
From my current understanding, log file is visible after a timekey interval or a buffer size.
If we configure with short time range there should have many files generated in case log content itself is not big.
If we configure with large time range then we need wait quite some time for log visibility.
Describe the solution you'd like
S3 support append semantic, so maybe we can implement with append file instead of put semantic.
Describe alternatives you've considered
File/WebHdfs plugin seems support append files.
Additional context
No response
The text was updated successfully, but these errors were encountered: