SEZ9 commented on issue #12923:
URL: https://github.com/apache/seatunnel/issues/12923#issuecomment-6816828149

   @taozhiyi13 Thanks for the update and for the careful tracing of the 
`MySqlTypeConverter` usages.
   
   The revised first-version scope looks right to me:
   
   - MySQL-CDC -> Zeta -> Elasticsearch/OpenSearch as the only new end-to-end 
path, with `GeometryType` / `Geometry` introduced on the CDC side, where there 
is no working historical contract for non-null spatial values.
   - The existing MySQL JDBC, MySQL-to-MySQL, TiDB, and StarRocks 
JDBC-compatible behavior stays unchanged. Your point that `ST_AsWKB(column)` 
drops MySQL's SRID prefix is a good reason to leave that path alone for now.
   - Documenting the strict full-cluster upgrade and restore boundary 
explicitly is exactly what I wanted to see.
   
   Holding implementation until the mailing-list discussion reaches consensus 
and the STIP is accepted is the right call. I'll weigh in on the one-PR vs. 
stacked-PRs question on the dev list so the decision is recorded in one place.
   
   One small ask: once the dev-list discussion settles, could you post a short 
summary of the outcome (scope confirmation and the chosen delivery model) back 
on this issue so the STIP record is self-contained?
   
   Nothing else needed from my side for now.
   
   <!-- streview-comment:2280 -->


-- 
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]

Reply via email to