terrymanu commented on issue #39196: URL: https://github.com/apache/shardingsphere/issues/39196#issuecomment-5058185844
Hi @alexalves83, thanks for the detailed report. This is a duplicate of #36081 and is a known database-type/dialect-selection bug, rather than a missing Doris grammar rule for the reported `DUPLICATE KEY`, `DISTRIBUTED BY HASH`, and `PROPERTIES` clauses. ShardingSphere 5.5.3 already includes those clauses in its Doris grammar and has a Doris parser integration case covering their combined use. The failure occurs earlier in dialect selection: Doris and MySQL both use the `jdbc:mysql:` URL prefix, and when both dialect modules are present, ShardingSphere resolves the storage type to the trunk MySQL type. ShardingSphere-Proxy then parses statements using that resolved logical-database protocol type, so the Doris parser module is not selected. The [5.5.3 Doris documentation](https://shardingsphere.apache.org/document/5.5.3/en/user-manual/shardingsphere-jdbc/optional-plugins/doris-fe/) documents this exact limitation and links to #36081. PR #36090 attempted to address the selection behavior but was closed without merge, and #36081 remains open with `status: blocked`; there is no merged fix or fixed release to verify yet. Please follow #36081 for the eventual resolution. I suggest labeling this issue as `type: duplicate`, `db: Doris`, and `in: infra`, then closing it as a duplicate. The standalone `MEDIUMINT` observation does not fully match the same explanation because both the MySQL and Doris grammars in 5.5.3 accept `MEDIUMINT`. If that statement still fails independently, please provide its exact unabridged exception and the effective Proxy protocol/database configuration as a focused follow-up, because it may use a different parser-selection path. -- 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]
