nzw921rx opened a new pull request, #11505: URL: https://github.com/apache/seatunnel/pull/11505
### Purpose of this pull request Add Zeta timer-flush support to the Elasticsearch sink, following the sink flush-action mechanism introduced in #10801 and the connector integration pattern from #10802. The writer registers its existing synchronized bulk flush operation through `SinkWriter.Context.registerFlushAction`, allowing buffered documents to become visible according to the environment-level `sink.flush.interval` without waiting for the batch threshold or a checkpoint. This initial implementation provides at-least-once delivery only. It does not provide 2PC exactly-once semantics, and retries can produce duplicate documents when deterministic document IDs are not configured. ### Does this PR introduce _any_ user-facing change? Yes. - Elasticsearch sink jobs running on Zeta can use `sink.flush.interval` to flush buffered documents periodically. - The English and Chinese connector documentation now describes Zeta-only timer flush behavior and the at-least-once limitation. ### How was this patch tested? - Added a Zeta-only E2E scenario that uses a batch threshold and checkpoint interval above the test workload, then verifies documents become visible while the job is still running. - `./mvnw spotless:apply` - `./mvnw -pl seatunnel-connectors-v2/connector-elasticsearch -DskipIT -DskipUT=false test` — 60 tests passed. - Elasticsearch connector E2E module `test-compile` completed successfully. The full container E2E was not executed locally because Maven `verify` was explicitly excluded from the validation run. ### Check list * [x] No new Jar binary package is added. * [x] English and Chinese connector documentation is updated. * [x] No incompatible configuration or API change is introduced. * [x] A connector E2E testcase is included. * [x] No plugin mapping, distribution dependency, CI label, or plugin configuration change is required for this existing connector. -- 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]
