SEZ9 commented on PR #11971: URL: https://github.com/apache/seatunnel/pull/11971#issuecomment-6118215355
Thanks for keeping the branch in sync. Since the change between `6907e2f2f8fb` and `e1d06f9021c7` looks like a merge from `dev` only, I'd like to confirm the status of the earlier points rather than assume they're closed: - **PR11971-F1** – Can you confirm `YashanDbCatalog` no longer closes the shared cached connection when checking for a single-physical-table query? - **PR11971-F2 / PR11971-F7** – Do the OceanBase/YashanDB overrides now bound the probe query (e.g. a row limit) and reuse a single `ResultSetMetaData`, and does the default catalog path avoid executing the user query twice? - **PR11971-F3** – Does `mergeWithUnderlyingTable` now load the metadata-verified origin `TablePath` rather than the query-derived identifier? - **PR11971-F4** – For drivers that report only a schema and no catalog, does the resolved `TablePath` still end up with a null database name? If so, `tableExists`/`getTable` would throw and the merge would silently fall back. Could you either handle the schema-only case explicitly or point me to where it is covered? - **PR11971-F5** – Is there a changelog entry describing `query_table_metadata_merge` and its `COMMENT` default? If not, please add one. - **PR11971-F6** – With `ALL`, query-only pipelines gain a merged primary key on upgrade, which affects split planning and sink auto-create DDL. Are the incompatible-changes notes updated for this? Alternatively, if `COMMENT` is intentionally the only behavior applied without opt-in, please state that explicitly in the docs. - **PR11971-F8** – Are fallback failures now logged at a visible level instead of being swallowed at `DEBUG`? A quick pointer to the relevant lines for each would be enough. Once those are confirmed I'm happy to do a final pass. <!-- streview-comment:1697 --> -- 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]
