suxiaogang223 opened a new pull request, #64389:
URL: https://github.com/apache/doris/pull/64389
### What problem does this PR solve?
Issue Number: None
Related PR: None
Problem Summary: 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 change
recognizes Doris-compatible version comments and keeps using the existing SHOW
FULL COLUMNS based type override path.
### 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 --run
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]
