DanielLeens commented on issue #12832: URL: https://github.com/apache/seatunnel/issues/12832#issuecomment-6266946983
Thanks for turning this into a concrete data-contract proposal. Classification: D / Connector-V2 cross-connector spatial data contract. I rechecked the current tree and the open/merged PR set: there is no existing SeaTunnel `GEOMETRY` carrier or competing implementation PR. However, adding a public type in `seatunnel-api` is not Zeta-only in effect; it also creates API, schema-serialization, and Flink/Spark translation obligations. Please do not open the implementation PR yet. First post a linked STIP/design that makes three contracts testable: (1) API/SPI and schema serialization compatibility, including deterministic rejection or support behavior in Flink and Spark; (2) the value and column-metadata representation across JDBC and Debezium snapshot/binlog paths; and (3) index creation, existing-index validation, SRID 4326 enforcement, malformed-WKB failures, and coordinate order for Elasticsearch/OpenSearch. The proposed no-reprojection boundary is sensible, but the STIP must also state how unsupported engines and existing schemas fail safely. Once that is agreed, the MySQL sources and Elasticsearch sink can be scoped into reviewable slices. -- 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]
