suxiaogang223 opened a new pull request, #64473:
URL: https://github.com/apache/doris/pull/64473
### What problem does this PR solve?
Issue Number: None
Related PR: #64389
Problem Summary: Pick #64389 to branch-4.1. JDBC catalog initializes the
MySQL client as a plain MySQL-compatible target unless the remote
version_comment contains the word Doris. Doris-compatible deployments can
expose version comments such as SelectDB, VeloDB, or enterprise cloud strings,
so Doris-specific column type overrides are skipped. As a result, Doris complex
types reported through MySQL metadata can be mapped as scalar MySQL types and
fail during scan. This pick recognizes Doris-compatible version comments and
keeps using the existing SHOW FULL COLUMNS based type override path.
Note: branch-4.1 does not have the newer fe-connector-jdbc module from
master, so this manual pick keeps only the existing fe-core JDBC client and
unit test changes.
### Release note
Fix JDBC catalog type mapping for Doris-compatible MySQL endpoints whose
version_comment does not contain Doris.
### Check List (For Author)
- Test: Unit Test
- ./run-fe-ut.sh
org.apache.doris.datasource.jdbc.client.JdbcMySQLClientTest
- Behavior changed: Yes. JDBC MySQL catalog now treats SelectDB, VeloDB, and
enterprise cloud version comments as Doris-compatible for column type mapping.
- Does this need documentation: No
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
