DanielLeens commented on PR #10801: URL: https://github.com/apache/seatunnel/pull/10801#issuecomment-4703715619
Thanks for clarifying. If precise/exactly-once support is intentionally out of scope for the 3.0 timer-flush rollout, then I am fine treating that as a deferred follow-up rather than a blocker on this branch. Since there is no new code on the PR head after my last review, I am not doing another full re-review in this pass. If this PR keeps moving, please keep the current limitation explicit in the docs / release notes so users do not assume the JDBC timer-flush path already covers exactly-once semantics. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
