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
add the ability to define a segment size or time interval after which the .tmp file is rotated and events sent to output.
for example at the moment we have just a couple of mapping errors per day. the .tmp file is a few kb in size. with this rate you can calculate how long it would take until it reaches 10mb.
having to restart the pipeline on a daily basis in order to have dlq events ingested does not seem reasonable at all.
would be nice if the documentation also said anything about the segment size limitation.
The text was updated successfully, but these errors were encountered:
add the ability to define a segment size or time interval after which the .tmp file is rotated and events sent to output.
for example at the moment we have just a couple of mapping errors per day. the .tmp file is a few kb in size. with this rate you can calculate how long it would take until it reaches 10mb.
having to restart the pipeline on a daily basis in order to have dlq events ingested does not seem reasonable at all.
would be nice if the documentation also said anything about the segment size limitation.
The text was updated successfully, but these errors were encountered: