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

   @taozhiyi13 Thanks for the ping, and sorry it went unanswered. The 
delivery-model question (one PR vs. stacked PRs) is still open on my side: 
nothing on this issue records an answer to it yet, and the right place to 
settle it is the `dev@` thread you linked: 
https://lists.apache.org/thread.html/b1jzjpq29qf1bogszzol7q4ykkg27ttf
   
   The text of your follow-up isn't on this issue, so I can't respond to its 
specifics here. Two things would help close this out:
   
   - Could you paste a short summary of the follow-up here, covering which 
option you prefer and why, and how the revised delivery slices would map onto 
PRs under the stacked option?
   - Once the `dev@` discussion converges, please post the outcome here so the 
STIP and the issue stay in sync.
   
   On the rest of your update, the first-version scope you wrote into the STIP 
matches what was discussed here:
   
   - MySQL-CDC -> Zeta -> Elasticsearch/OpenSearch is the first-version path.
   - Existing MySQL JDBC, MySQL-to-MySQL, TiDB, and StarRocks JDBC-compatible 
behavior stays unchanged.
   - The strict full-cluster upgrade and restore boundary is documented.
   
   Holding implementation until the mailing-list discussion reaches consensus 
and the STIP is accepted is the right order, so nothing further is needed from 
you on the scope itself.
   
   <!-- streview-comment:2431 -->


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