linghengqian opened a new issue, #37500: URL: https://github.com/apache/shardingsphere/issues/37500
## Feature Request **For English only**, other languages will not be accepted. Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot make decision by current information, we will **close it**. Please answer these questions before submitting your issue. Thanks! ### Is your feature request related to a problem? - No. ### Describe the feature you would like. - Remove support for `DerbyNetworkServer` and `EmbeddedDerby` from `JDBCRepository`. This idea came from an announcement at https://db.apache.org/derby/ and https://issues.apache.org/jira/browse/INFRA-27383 . > Derby Retired > On 2025-10-10, the Derby developers voted to retire the project into a read-only state. Derby development and bug-fixing have ended. No further releases will be published. The Derby website and wiki are frozen in place. Derby JIRA issues are now read-only and new bugs cannot be logged. The user and developer lists are disabled and can be accessed only through their archives. - The documentation is available at https://shardingsphere.apache.org/document/current/en/user-manual/common-config/builtin-algorithm/metadata-repository/ and https://shardingsphere.apache.org/document/current/cn/user-manual/common-config/builtin-algorithm/metadata-repository/ . The relevant files are all located at https://github.com/apache/shardingsphere/tree/b5fca38c509df6eebce8dbe309ce82fdf9a99d25/mode/type/standalone/repository/provider/jdbc/src/main/resources/sql . - In fact, I had not previously added any integration tests for `DerbyNetworkServer` and `EmbeddedDerby` to the master branch because the derby documentation had been broken for several years and there were multiple issues being tracked. - https://issues.apache.org/jira/browse/DERBY-7166 - https://issues.apache.org/jira/browse/DERBY-7165 - https://issues.apache.org/jira/browse/DERBY-7108 - Since the original issue on the derby side will never be resolved, there's no need to maintain support for derby. -- 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]
