Q2K3 opened a new issue, #30754: URL: https://github.com/apache/shardingsphere/issues/30754
As above, memory mode has been removed since V5.2.0. Using it in V5.2.0 or higher version (not test yet) will get an exception with message below > SPI-00001: No implementation class load from SPI `org.apache.shardingsphere.mode.manager.ContextManagerBuilder` with type `Memory`. Things about why 'memory mode' was suddenly and quietly removed without compatibility are another question to care about later. But now there are some points I want to suggest: - Adding clear log which removing memory mode into V5.2.0 release log. (help user realize removing directly) - Adding clear highlight which removing memory mode in V5.2.0 and higher version [document](https://shardingsphere.apache.org/document/). (good documents should alert user about deprecated or removing features) - Last, there are some official examples in tag [V5.2.0](https://github.com/apache/shardingsphere/blob/5.2.0/examples/shardingsphere-jdbc-example/single-feature-example/sharding-example/sharding-spring-boot-mybatis-example/src/main/resources/application-sharding-tables.properties) / [V5.2.1](https://github.com/apache/shardingsphere/blob/5.2.1/examples/shardingsphere-jdbc-example/single-feature-example/sharding-example/sharding-spring-boot-mybatis-example/src/main/resources/application-sharding-tables.properties) (not cover all) still using memory mode in application.properties file. examples mentioned above seem not to work as expect. I suppose there has need to recheck examples and fix them. Thks for all contributors in this project and waiting for your response and discussion. -- 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]
