terrymanu commented on issue #14899: URL: https://github.com/apache/shardingsphere/issues/14899#issuecomment-5390816292
Hi @TeslaCN, this enhancement can be closed because its original umbrella goal has been delivered on current master. [#22401](https://github.com/apache/shardingsphere/pull/22401) introduced the dedicated ShardingSphere-Proxy `passthrough` scenario, and the related and follow-up changes added representative data-type coverage for MySQL, PostgreSQL, and openGauss. The scenario remains part of the Proxy/Cluster nightly matrix, and the latest completed nightly passed for all three databases. There are two qualifications. First, the original “no explicitly configured feature rules” condition is no longer literally true: since [#26334](https://github.com/apache/shardingsphere/pull/26334), the three configurations use only `!SINGLE` to load and manage their test tables under the current single-table model. They do not configure sharding, encryption, read/write splitting, or other business rules. Second, closing this issue should not imply that every native database type is covered. The issue did not define an exhaustive type matrix, and a few disabled cases remain; those should be tracked through focused follow-up issues if they are still required. Recommended action: add `type: enhancement`, keep `in: proxy` and `in: test`, and close this issue as completed at the original intent level. -- 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]
