DanielLeens commented on issue #12704: URL: https://github.com/apache/seatunnel/issues/12704#issuecomment-6367124929
Thanks for following up. Classification: A / Connector-V2 Elasticsearch/OpenSearch document identity and data correctness. Current `dev` still builds an Elasticsearch composite `_id` by concatenating formatted primary-key values with `key_delimiter`, so the collision described here remains possible. Merged #12839 is useful precedent: it added an opt-in collision-safe encoding for Easysearch and Typesense. It is not an automatic Elasticsearch fix, but it supports the direction. #12705 was closed after an `ACTION_REQUIRED` Build/workflow-detection problem rather than a technical rejection. Please either revive #12705 on current `dev` or open one focused replacement PR. It must preserve the existing delimiter-based IDs by default for compatibility and make the collision-safe representation an explicit opt-in choice. Please include tests for colliding tuples, the legacy default, single keys, null values, and the Elasticsearch/OpenSearch serialization path. An integration assertion that the two formerly colliding rows remain distinct would complete the evidence. There is no competing active Elasticsearch/OpenSearch implementation at this point, so a rebased focused contribution is welcome. -- 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]
