SEPURI-SAI-KRISHNA commented on PR #13243: URL: https://github.com/apache/seatunnel/pull/13243#issuecomment-6999860710
@SEZ9 @DanielLeens thanks. `d1d829d426` covers the documentation side, in EN and ZH: - F1: the upgrade note now says plainly that what such a checkpoint's writer state still holds, for example commits prepared but not yet committed, is abandoned. - F2: `multi-table.md` and the upgrade note say the check runs after the save mode on a fresh start, so a destructive save mode may already have cleared or recreated the targets. - F7: the `KEYED` text (multi-table, common options, Jdbc) notes that a `BYTES` key is hashed by array identity; keep one replica for such tables until content hashing (#13242) lands. - F3: every non-Jdbc sink page that lists the option now says to keep it at 1, including the sections and examples that invited raising it; `schema-evolution.md` is qualified as Jdbc with a primary key. - F8: "with 1 and the same sink parallelism". - F9: the Mysql, PostgreSql, Oracle, OceanBase, SqlServer, Redshift and DuckDB rows state both Jdbc rules, linking the Jdbc note. The code side of F1, F2 and F7 stays open for the dev@ design after 3.1.0. -- 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]
