SEZ9 commented on issue #12988: URL: https://github.com/apache/seatunnel/issues/12988#issuecomment-6620805719
@SEPURI-SAI-KRISHNA confirmed, thanks. Since the description of #13090 already carries `Closes #12988` and GitHub shows this issue under the PR's linked issues, there is nothing more to do on the linking side; this issue will close automatically when #13090 merges, and I will not close it manually before then. On the root cause, your explanation matches what @zhangwen0527 reported: in 3.0.0 `ElasticsearchVersion` only knows the major versions 2, 5, 6, 7 and 8, the sink resolves the cluster version in `ElasticsearchSinkWriter.initializeSerializer`, so every sink job against 9.x fails with the `ELASTICSEARCH-02 ... version=9` error seen in job 1169512690318573569. Your side-by-side run (0 documents with the 3.0.0 version list, 20 of 20 rows written with #13090) is exactly the evidence we need attached to the PR. @zhangwen0527 to summarize for you: there is no workaround in 3.0.0 because the version check reads from the cluster and no sink option skips it. The fix is the `ES9` value added in #13090 and will be in the next release after it merges. If you can build from the PR branch and rerun your `face20261021.json` job against 9.5.5, a short note here on whether `t_face_vector` is populated would be a useful confirmation, but it is not blocking. Remaining ask: none beyond the optional verification above; I will leave this issue open to be closed by #13090. <!-- streview-comment:2255 --> -- 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]
