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
For jdbc multiple sink and other multiple sinks, when invoke is more frequent then the scheduler's batch interval, the dirty data will flush at a faster rate.
What you expected to happen
let's say the batch interval is 60000. if I call dirtySink.invoke every 1 second, it will invoke, then flush 1-2 records every one second, instead of the 60s which the batch interval is supposed to be.
How to reproduce
let's say the batch interval is 60000. if I call dirtySink.invoke every 1 second, it will invoke, then flush 1-2 records every one second, instead of the 60s which the batch interval is supposed to be.
What happened
For jdbc multiple sink and other multiple sinks, when invoke is more frequent then the scheduler's batch interval, the dirty data will flush at a faster rate.
What you expected to happen
let's say the batch interval is 60000. if I call dirtySink.invoke every 1 second, it will invoke, then flush 1-2 records every one second, instead of the 60s which the batch interval is supposed to be.
How to reproduce
let's say the batch interval is 60000. if I call dirtySink.invoke every 1 second, it will invoke, then flush 1-2 records every one second, instead of the 60s which the batch interval is supposed to be.
Environment
No response
InLong version
master
InLong Component
InLong Sort
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: