davidzollo commented on issue #11021: URL: https://github.com/apache/seatunnel/issues/11021#issuecomment-5578840292
> There are 7 bug fix PRs left to be merged before the 3.0.0 release: > > * [[Fix][CDC][Zeta] Restore runtime schema from checkpoint after failover #11503](https://github.com/apache/seatunnel/pull/11503) [@nielifeng](https://github.com/nielifeng) > * [[Bug][Zeta] Fix stale taskDone removing execution context of a newer restore generation (#11755) #11757](https://github.com/apache/seatunnel/pull/11757) [@waterWang](https://github.com/waterWang) > * [[Fix][Zeta] Reuse fixed slots after master failover #11458](https://github.com/apache/seatunnel/pull/11458) [@zhangshenghang](https://github.com/zhangshenghang) > * [[Fix][Zeta] Release the start latch when a blocking worker cannot start (#11679) #11727](https://github.com/apache/seatunnel/pull/11727) [@abdessalems](https://github.com/abdessalems) > * [fix: reuse shared SinkWriter for same destination in multi-table sink #11077](https://github.com/apache/seatunnel/pull/11077) [@hesam-oxe](https://github.com/hesam-oxe) > * [[Fix][Connector-V2] Propagate JDBC XA commit failures #11569](https://github.com/apache/seatunnel/pull/11569) [@DanielLeens](https://github.com/DanielLeens) > * [[Bug][Connector-V2][CDC] Prune removed tables from restored incremental splits #11271](https://github.com/apache/seatunnel/pull/11271) [@hutiefang76](https://github.com/hutiefang76) [fix: reuse shared SinkWriter for same destination in multi-table sink #11077](https://github.com/apache/seatunnel/pull/11077) [@hesam-oxe](https://github.com/hesam-oxe) is an improvement for SeaTunnel, this will not affect the release. Now there are 4 bug fix PRs left to be merged before the 3.0.0 release: - https://github.com/apache/seatunnel/pull/11503 @nielifeng - https://github.com/apache/seatunnel/pull/11757 @waterWang - https://github.com/apache/seatunnel/pull/11458 @zhangshenghang - https://github.com/apache/seatunnel/pull/11727 @abdessalems -- 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]
