suxiaogang223 opened a new pull request, #68008:
URL: https://github.com/apache/doris/pull/68008

   ### What problem does this PR solve?
   
   Related PR: #64389
   
   JDBC Catalog can misidentify an enterprise Doris endpoint as MySQL when its 
`version_comment` is `enterprise version enterprise-4.1.4-rc01-a317601ce72`, 
without the optional `(Cloud Mode)` suffix. The existing detection requires 
that suffix, so both the legacy JDBC client and the connector JDBC client skip 
Doris-specific type mapping and `SHOW FULL COLUMNS` type overrides.
   
   This can expose `ARRAY<TINYINT>` as `TINYINT`, causing `ArrayStoreException` 
when scanning array text, and misidentify `LARGEINT`, `HLL`, and `BITMAP`, 
causing incorrect schemas or aggregation errors.
   
   Recognize the `enterprise version enterprise-` prefix in both clients while 
retaining the existing recognition rules. Extend both unit tests with the 
reported version string, an uppercase variant, and MySQL Enterprise negative 
cases. Existing end-to-end cases retain their expected results.
   
   ### Release note
   
   Fix JDBC Catalog type mapping for enterprise Doris endpoints whose version 
comment omits the Cloud Mode suffix.
   
   ### Check List (For Author)
   
   - Test: Static checks passed
       - Checkstyle for `fe-core` and `fe-connector-jdbc`
       - Connector import and metadata funnel checks
       - `git diff --check`
       - Unit tests added but not run locally: the worktree lacks thirdparty 
`protoc`
       - Cluster regression tests not run locally: no built cluster in the 
worktree
   - Behavior changed: Yes, enterprise endpoints without the cloud suffix use 
Doris-specific 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]

Reply via email to