You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by "azrulmSE (via GitHub)" <gi...@apache.org> on 2023/02/03 10:25:52 UTC

[GitHub] [shardingsphere] azrulmSE opened a new issue, #23973: sharding-jdbc 5.3.1: The Rule of ReadWrite-Splitting does not work

azrulmSE opened a new issue, #23973:
URL: https://github.com/apache/shardingsphere/issues/23973

   ## Bug Report
   
   ### Which version of ShardingSphere did you use?
   - 5.3.1
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   - shardingsphere-jdbc-core
   Here the pom.xml file configuration:
   ```
   <?xml version="1.0" encoding="UTF-8"?>
   <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
   	<modelVersion>4.0.0</modelVersion>
   	<parent>
   		<groupId>org.springframework.boot</groupId>
   		<artifactId>spring-boot-starter-parent</artifactId>
   		<version>2.7.7</version>
   		<relativePath/> <!-- lookup parent from repository -->
   	</parent>
   	<groupId>com.shard</groupId>
   	<artifactId>sharding-jdbc</artifactId>
   	<version>0.0.1-SNAPSHOT</version>
   	<name>sharding-jdbc</name>
   	<description>Demo project for Spring Boot</description>
   	<properties>
   		<java.version>17</java.version>
   	</properties>
   	<dependencies>
   		<dependency>
   			<groupId>org.springframework.boot</groupId>
   			<artifactId>spring-boot-starter-web</artifactId>
   		</dependency>
   		<dependency>
   			<groupId>org.springframework.boot</groupId>
   			<artifactId>spring-boot-starter-data-jpa</artifactId>
   		</dependency>
   
   		<dependency>
   			<groupId>org.springframework.boot</groupId>
   			<artifactId>spring-boot-devtools</artifactId>
   			<scope>runtime</scope>
   			<optional>true</optional>
   		</dependency>
   		<dependency>
   	        <groupId>org.springframework.boot</groupId>
   	        <artifactId>spring-boot-configuration-processor</artifactId>
   	        <optional>true</optional>
   	    </dependency>
   		<dependency>
   		    <groupId>org.apache.shardingsphere</groupId>
   		    <artifactId>shardingsphere-jdbc-core</artifactId>
   		    <version>5.3.1</version>
   		</dependency>
   		<dependency>
   			<groupId>com.mysql</groupId>
   			<artifactId>mysql-connector-j</artifactId>
   			<scope>runtime</scope>
   		</dependency>
   		<dependency>
   			<groupId>org.projectlombok</groupId>
   			<artifactId>lombok</artifactId>
   			<optional>true</optional>
   		</dependency>
   		<dependency>
   			<groupId>org.springframework.boot</groupId>
   			<artifactId>spring-boot-starter-test</artifactId>
   			<scope>test</scope>
   		</dependency>
   		<!-- https://mvnrepository.com/artifact/org.apache.commons/commons-lang3 
   		<dependency>
   		    <groupId>org.apache.commons</groupId>
   		    <artifactId>commons-lang3</artifactId>
   		    <version>3.12.0</version>
   		</dependency>-->
   		<dependency>
               <groupId>org.yaml</groupId>
               <artifactId>snakeyaml</artifactId>
               <version>1.33</version>
           </dependency>
   	</dependencies>
   
   	<build>
   		<plugins>
   			<plugin>
   				<groupId>org.springframework.boot</groupId>
   				<artifactId>spring-boot-maven-plugin</artifactId>
   				<configuration>
   					<excludes>
   						<exclude>
   							<groupId>org.projectlombok</groupId>
   							<artifactId>lombok</artifactId>
   						</exclude>
   					</excludes>
   				</configuration>
   			</plugin>
   		</plugins>
   	</build>
   </project>
   
   ```
   
   - MySQL version:
   ![image](https://user-images.githubusercontent.com/3959366/216565924-9590ed80-8e6f-48e2-abf1-5ca576c88ff8.png)
   
   - Config File: config.yaml
   ```
   mode:
     type: Standalone
     repository:
       type: JDBC
       
   dataSources:
     ds_1:
       dataSourceClassName: com.zaxxer.hikari.HikariDataSource
       driverClassName: com.mysql.jdbc.Driver
       jdbcUrl: jdbc:mysql://localhost:3306/db0?serverTimezone=UTC&useSSL=false&allowPublicKeyRetrieval=true&createDatabaseIfNotExist=true
       username: root
       password: MySecretPass
     ds_2:
       dataSourceClassName: com.zaxxer.hikari.HikariDataSource
       driverClassName: com.mysql.jdbc.Driver
       jdbcUrl: jdbc:mysql://localhost:3306/db1?serverTimezone=UTC&useSSL=false&allowPublicKeyRetrieval=true&createDatabaseIfNotExist=true
       username: root
       password: MySecretPass
     ds_3:
       dataSourceClassName: com.zaxxer.hikari.HikariDataSource
       driverClassName: com.mysql.jdbc.Driver
       jdbcUrl: jdbc:mysql://localhost:3306/db2?serverTimezone=UTC&useSSL=false&allowPublicKeyRetrieval=true&createDatabaseIfNotExist=true
       username: root
       password: MySecretPass
       
   rules:
   - !READWRITE_SPLITTING
     dataSources:
       readwrite_ds:
         staticStrategy:
           writeDataSourceName: ds_1
           readDataSourceNames:
             - ds_2
             - ds_3
         loadBalancerName: round_robin
     loadBalancers:
       round_robin:
         type: ROUND_ROBIN
   
   props:
     sql-show: true
   ```
   
   ### Expected behavior
   - Normal start
   
   ### Actual behavior
   - Hit this error on log, here the log:
   ```
   17:57:50.686 [Thread-0] DEBUG org.springframework.boot.devtools.restart.classloader.RestartClassLoader - Created RestartClassLoader org.springframework.boot.devtools.restart.classloader.RestartClassLoader@2c3f29c
   2023-02-03 17:57:51.103  INFO 73848 --- [  restartedMain] com.shard.ShardingJdbcApplication        : Starting ShardingJdbcApplication using Java 17 on DESKTOP-R6PJPBR with PID 73848 (D:\development\sharding-jdbc\target\classes started by user in D:\development\sharding-jdbc)
   2023-02-03 17:57:51.113  INFO 73848 --- [  restartedMain] com.shard.ShardingJdbcApplication        : No active profile set, falling back to 1 default profile: "default"
   2023-02-03 17:57:51.360  INFO 73848 --- [  restartedMain] .e.DevToolsPropertyDefaultsPostProcessor : For additional web related logging consider setting the 'logging.level.web' property to 'DEBUG'
   2023-02-03 17:57:51.910  INFO 73848 --- [  restartedMain] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFAULT mode.
   2023-02-03 17:57:51.953  INFO 73848 --- [  restartedMain] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 34 ms. Found 1 JPA repository interfaces.
   2023-02-03 17:57:52.395  INFO 73848 --- [  restartedMain] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 8080 (http)
   2023-02-03 17:57:52.404  INFO 73848 --- [  restartedMain] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
   2023-02-03 17:57:52.405  INFO 73848 --- [  restartedMain] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.70]
   2023-02-03 17:57:52.919  INFO 73848 --- [  restartedMain] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
   2023-02-03 17:57:52.919  INFO 73848 --- [  restartedMain] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 1558 ms
   2023-02-03 17:57:53.087  INFO 73848 --- [  restartedMain] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...
   2023-02-03 17:57:53.271  INFO 73848 --- [  restartedMain] com.zaxxer.hikari.HikariDataSource       : HikariPool-2 - Starting...
   2023-02-03 17:57:53.454  INFO 73848 --- [  restartedMain] com.zaxxer.hikari.HikariDataSource       : HikariPool-2 - Start completed.
   2023-02-03 17:57:53.627  INFO 73848 --- [  restartedMain] com.zaxxer.hikari.HikariDataSource       : HikariPool-3 - Starting...
   2023-02-03 17:57:53.826  INFO 73848 --- [  restartedMain] com.zaxxer.hikari.HikariDataSource       : HikariPool-3 - Start completed.
   2023-02-03 17:57:53.827  INFO 73848 --- [  restartedMain] com.zaxxer.hikari.HikariDataSource       : HikariPool-4 - Starting...
   2023-02-03 17:57:53.842  INFO 73848 --- [  restartedMain] com.zaxxer.hikari.HikariDataSource       : HikariPool-4 - Start completed.
   2023-02-03 17:57:53.842  INFO 73848 --- [  restartedMain] com.zaxxer.hikari.HikariDataSource       : HikariPool-5 - Starting...
   2023-02-03 17:57:53.855  INFO 73848 --- [  restartedMain] com.zaxxer.hikari.HikariDataSource       : HikariPool-5 - Start completed.
   2023-02-03 17:57:54.688  INFO 73848 --- [  restartedMain] com.zaxxer.hikari.pool.PoolBase          : HikariPool-1 - Driver does not support get/set network timeout for connections. (getNetworkTimeout)
   2023-02-03 17:57:54.690  INFO 73848 --- [  restartedMain] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Start completed.
   2023-02-03 17:57:54.732  INFO 73848 --- [  restartedMain] o.hibernate.jpa.internal.util.LogHelper  : HHH000204: Processing PersistenceUnitInfo [name: default]
   2023-02-03 17:57:54.807  INFO 73848 --- [  restartedMain] org.hibernate.Version                    : HHH000412: Hibernate ORM core version 5.6.14.Final
   2023-02-03 17:57:55.009  INFO 73848 --- [  restartedMain] o.hibernate.annotations.common.Version   : HCANN000001: Hibernate Commons Annotations {5.1.2.Final}
   2023-02-03 17:57:55.135  INFO 73848 --- [  restartedMain] org.hibernate.dialect.Dialect            : HHH000400: Using dialect: org.hibernate.dialect.MySQLDialect
   2023-02-03 17:57:55.661  WARN 73848 --- [  restartedMain] o.h.engine.jdbc.spi.SqlExceptionHelper   : SQL Error: 0, SQLState: null
   2023-02-03 17:57:55.661 ERROR 73848 --- [  restartedMain] o.h.engine.jdbc.spi.SqlExceptionHelper   : getStatement
   2023-02-03 17:57:55.665 ERROR 73848 --- [  restartedMain] j.LocalContainerEntityManagerFactoryBean : Failed to initialize JPA EntityManagerFactory: [PersistenceUnit: default] Unable to build Hibernate SessionFactory; nested exception is org.hibernate.exception.GenericJDBCException: Error accessing table metadata
   2023-02-03 17:57:55.666  WARN 73848 --- [  restartedMain] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in class path resource [org/springframework/boot/autoconfigure/orm/jpa/HibernateJpaConfiguration.class]: Invocation of init method failed; nested exception is javax.persistence.PersistenceException: [PersistenceUnit: default] Unable to build Hibernate SessionFactory; nested exception is org.hibernate.exception.GenericJDBCException: Error accessing table metadata
   2023-02-03 17:57:55.667  INFO 73848 --- [  restartedMain] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Shutdown initiated...
   2023-02-03 17:57:55.669  INFO 73848 --- [  restartedMain] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Shutdown completed.
   2023-02-03 17:57:55.670  INFO 73848 --- [  restartedMain] o.apache.catalina.core.StandardService   : Stopping service [Tomcat]
   2023-02-03 17:57:55.680  INFO 73848 --- [  restartedMain] ConditionEvaluationReportLoggingListener : 
   
   Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
   2023-02-03 17:57:55.704 ERROR 73848 --- [  restartedMain] o.s.boot.SpringApplication               : Application run failed
   
   org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in class path resource [org/springframework/boot/autoconfigure/orm/jpa/HibernateJpaConfiguration.class]: Invocation of init method failed; nested exception is javax.persistence.PersistenceException: [PersistenceUnit: default] Unable to build Hibernate SessionFactory; nested exception is org.hibernate.exception.GenericJDBCException: Error accessing table metadata
   	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1804) ~[spring-beans-5.3.24.jar:5.3.24]
   	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:620) ~[spring-beans-5.3.24.jar:5.3.24]
   	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542) ~[spring-beans-5.3.24.jar:5.3.24]
   	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335) ~[spring-beans-5.3.24.jar:5.3.24]
   	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) ~[spring-beans-5.3.24.jar:5.3.24]
   	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333) ~[spring-beans-5.3.24.jar:5.3.24]
   	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208) ~[spring-beans-5.3.24.jar:5.3.24]
   	at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1154) ~[spring-context-5.3.24.jar:5.3.24]
   	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:908) ~[spring-context-5.3.24.jar:5.3.24]
   	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:583) ~[spring-context-5.3.24.jar:5.3.24]
   	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:147) ~[spring-boot-2.7.7.jar:2.7.7]
   	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:731) ~[spring-boot-2.7.7.jar:2.7.7]
   	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:408) ~[spring-boot-2.7.7.jar:2.7.7]
   	at org.springframework.boot.SpringApplication.run(SpringApplication.java:307) ~[spring-boot-2.7.7.jar:2.7.7]
   	at com.shard.ShardingJdbcApplication.main(ShardingJdbcApplication.java:13) ~[classes/:na]
   	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:na]
   	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[na:na]
   	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:na]
   	at java.base/java.lang.reflect.Method.invoke(Method.java:568) ~[na:na]
   	at org.springframework.boot.devtools.restart.RestartLauncher.run(RestartLauncher.java:49) ~[spring-boot-devtools-2.7.7.jar:2.7.7]
   Caused by: javax.persistence.PersistenceException: [PersistenceUnit: default] Unable to build Hibernate SessionFactory; nested exception is org.hibernate.exception.GenericJDBCException: Error accessing table metadata
   	at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.buildNativeEntityManagerFactory(AbstractEntityManagerFactoryBean.java:421) ~[spring-orm-5.3.24.jar:5.3.24]
   	at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:396) ~[spring-orm-5.3.24.jar:5.3.24]
   	at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.afterPropertiesSet(LocalContainerEntityManagerFactoryBean.java:341) ~[spring-orm-5.3.24.jar:5.3.24]
   	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1863) ~[spring-beans-5.3.24.jar:5.3.24]
   	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1800) ~[spring-beans-5.3.24.jar:5.3.24]
   	... 19 common frames omitted
   Caused by: org.hibernate.exception.GenericJDBCException: Error accessing table metadata
   	at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:42) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   	at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:113) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   	at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:99) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   	at org.hibernate.tool.schema.extract.internal.AbstractInformationExtractorImpl.convertSQLException(AbstractInformationExtractorImpl.java:124) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   	at org.hibernate.tool.schema.extract.internal.AbstractInformationExtractorImpl.getTables(AbstractInformationExtractorImpl.java:577) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   	at org.hibernate.tool.schema.extract.internal.DatabaseInformationImpl.getTablesInformation(DatabaseInformationImpl.java:122) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   	at org.hibernate.tool.schema.internal.GroupedSchemaMigratorImpl.performTablesMigration(GroupedSchemaMigratorImpl.java:68) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   	at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.performMigration(AbstractSchemaMigrator.java:220) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   	at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.doMigration(AbstractSchemaMigrator.java:123) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   	at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.performDatabaseAction(SchemaManagementToolCoordinator.java:196) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   	at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.process(SchemaManagementToolCoordinator.java:85) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   	at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:335) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   	at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:471) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   	at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1498) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   	at org.springframework.orm.jpa.vendor.SpringHibernateJpaPersistenceProvider.createContainerEntityManagerFactory(SpringHibernateJpaPersistenceProvider.java:58) ~[spring-orm-5.3.24.jar:5.3.24]
   	at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:365) ~[spring-orm-5.3.24.jar:5.3.24]
   	at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.buildNativeEntityManagerFactory(AbstractEntityManagerFactoryBean.java:409) ~[spring-orm-5.3.24.jar:5.3.24]
   	... 23 common frames omitted
   Caused by: java.sql.SQLFeatureNotSupportedException: getStatement
   	at org.apache.shardingsphere.driver.jdbc.unsupported.AbstractUnsupportedDatabaseMetaDataResultSet.getStatement(AbstractUnsupportedDatabaseMetaDataResultSet.java:92) ~[shardingsphere-jdbc-core-5.3.1.jar:5.3.1]
   	at com.zaxxer.hikari.pool.ProxyDatabaseMetaData.getTables(ProxyDatabaseMetaData.java:69) ~[HikariCP-4.0.3.jar:na]
   	at com.zaxxer.hikari.pool.HikariProxyDatabaseMetaData.getTables(HikariProxyDatabaseMetaData.java) ~[HikariCP-4.0.3.jar:na]
   	at org.hibernate.tool.schema.extract.internal.InformationExtractorJdbcDatabaseMetaDataImpl.processTableResultSet(InformationExtractorJdbcDatabaseMetaDataImpl.java:64) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   	at org.hibernate.tool.schema.extract.internal.AbstractInformationExtractorImpl.getTables(AbstractInformationExtractorImpl.java:565) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   	... 35 common frames omitted
   ```
   ### Reason analyze (If you can)
   
   -  I following this instruction to run the rule for readwrite-splitting, here the [links](https://shardingsphere.apache.org/document/5.3.1/en/user-manual/shardingsphere-jdbc/yaml-config/rules/readwrite-splitting/)
   
   ### Steps to reproduce the behavior
   - Run the project from the github given
   
   ### Example codes for reproduce this issue (such as a github link).
   -  Here I provide the link of github to produce the error [link](https://github.com/azrulmSE/spring-boot-readwrite-split)
   


-- 
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: notifications-unsubscribe@shardingsphere.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] TeslaCN commented on issue #23973: sharding-jdbc 5.3.1: The Rule of ReadWrite-Splitting does not work

Posted by "TeslaCN (via GitHub)" <gi...@apache.org>.
TeslaCN commented on issue #23973:
URL: https://github.com/apache/shardingsphere/issues/23973#issuecomment-1426918142

   > Hi, is there a way for me to be aware that this integration issue going to be fix in the future?
   
   Would you like to try fixing this issue?


-- 
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: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] azrulmSE commented on issue #23973: sharding-jdbc 5.3.1: The Rule of ReadWrite-Splitting does not work

Posted by "azrulmSE (via GitHub)" <gi...@apache.org>.
azrulmSE commented on issue #23973:
URL: https://github.com/apache/shardingsphere/issues/23973#issuecomment-1416645171

   > Thanks for your report.
   > 
   > The root cause of this issue is ShardingSphere didn't implemented the method `getStatement` of `DatabaseMetaDataResultSet`.
   > 
   > ```
   > Caused by: java.sql.SQLFeatureNotSupportedException: getStatement
   > 	at org.apache.shardingsphere.driver.jdbc.unsupported.AbstractUnsupportedDatabaseMetaDataResultSet.getStatement(AbstractUnsupportedDatabaseMetaDataResultSet.java:92) ~[shardingsphere-jdbc-core-5.3.1.jar:5.3.1]
   > 	at com.zaxxer.hikari.pool.ProxyDatabaseMetaData.getTables(ProxyDatabaseMetaData.java:69) ~[HikariCP-4.0.3.jar:na]
   > 	at com.zaxxer.hikari.pool.HikariProxyDatabaseMetaData.getTables(HikariProxyDatabaseMetaData.java) ~[HikariCP-4.0.3.jar:na]
   > 	at org.hibernate.tool.schema.extract.internal.InformationExtractorJdbcDatabaseMetaDataImpl.processTableResultSet(InformationExtractorJdbcDatabaseMetaDataImpl.java:64) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   > 	at org.hibernate.tool.schema.extract.internal.AbstractInformationExtractorImpl.getTables(AbstractInformationExtractorImpl.java:565) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   > 	... 35 common frames omitted
   > ```
   
   Is that mean there nothing wrong with my configuration, right?


-- 
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: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] TeslaCN closed issue #23973: sharding-jdbc 5.3.1: The Rule of ReadWrite-Splitting does not work

Posted by "TeslaCN (via GitHub)" <gi...@apache.org>.
TeslaCN closed issue #23973: sharding-jdbc 5.3.1: The Rule of ReadWrite-Splitting does not work
URL: https://github.com/apache/shardingsphere/issues/23973


-- 
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: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] TeslaCN commented on issue #23973: sharding-jdbc 5.3.1: The Rule of ReadWrite-Splitting does not work

Posted by "TeslaCN (via GitHub)" <gi...@apache.org>.
TeslaCN commented on issue #23973:
URL: https://github.com/apache/shardingsphere/issues/23973#issuecomment-1427237195

   > > > Hi, is there a way for me to be aware that this integration issue going to be fix in the future?
   > > 
   > > 
   > > Would you like to try fixing this issue?
   > 
   > I want to fix this issue. But hava a question: why `AbstractUnsupportedDatabaseMetaDataResultSet#getStatement` is a not support operation
   
   I think we just didn't intent to implement it before. 
   
   We could try `getStatement` from the `resultSet` and implement the `getStatement` method in `DatabaseMetaDataResultSet`.
   https://github.com/apache/shardingsphere/blob/c4412e1cc302cbd9b82bf9b40f0f9cbcf9d25be5/jdbc/core/src/main/java/org/apache/shardingsphere/driver/jdbc/core/resultset/DatabaseMetaDataResultSet.java#L74-L82


-- 
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: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] azrulmSE commented on issue #23973: sharding-jdbc 5.3.1: The Rule of ReadWrite-Splitting does not work

Posted by "azrulmSE (via GitHub)" <gi...@apache.org>.
azrulmSE commented on issue #23973:
URL: https://github.com/apache/shardingsphere/issues/23973#issuecomment-1426650556

   Hi, is there a way for me to be aware that this integration issue going to be fix in the future?


-- 
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: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] GuoHaoZai commented on issue #23973: sharding-jdbc 5.3.1: The Rule of ReadWrite-Splitting does not work

Posted by "GuoHaoZai (via GitHub)" <gi...@apache.org>.
GuoHaoZai commented on issue #23973:
URL: https://github.com/apache/shardingsphere/issues/23973#issuecomment-1427252528

   > > > > Hi, is there a way for me to be aware that this integration issue going to be fix in the future?
   > > > 
   > > > 
   > > > Would you like to try fixing this issue?
   > > 
   > > 
   > > I want to fix this issue. But hava a question: why `AbstractUnsupportedDatabaseMetaDataResultSet#getStatement` is a not support operation
   > 
   > I think we just didn't intent to implement it before.
   > 
   > We could try `getStatement` from the `resultSet` and implement the `getStatement` method in `DatabaseMetaDataResultSet`.
   > 
   > https://github.com/apache/shardingsphere/blob/c4412e1cc302cbd9b82bf9b40f0f9cbcf9d25be5/jdbc/core/src/main/java/org/apache/shardingsphere/driver/jdbc/core/resultset/DatabaseMetaDataResultSet.java#L74-L82
   
   ok


-- 
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: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] GuoHaoZai commented on issue #23973: sharding-jdbc 5.3.1: The Rule of ReadWrite-Splitting does not work

Posted by "GuoHaoZai (via GitHub)" <gi...@apache.org>.
GuoHaoZai commented on issue #23973:
URL: https://github.com/apache/shardingsphere/issues/23973#issuecomment-1426997006

   > > Hi, is there a way for me to be aware that this integration issue going to be fix in the future?
   > 
   > Would you like to try fixing this issue?
   
   I want to fix this issue. But hava a question: why `AbstractUnsupportedDatabaseMetaDataResultSet#getStatement` is a not support operation


-- 
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: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] TeslaCN commented on issue #23973: sharding-jdbc 5.3.1: The Rule of ReadWrite-Splitting does not work

Posted by "TeslaCN (via GitHub)" <gi...@apache.org>.
TeslaCN commented on issue #23973:
URL: https://github.com/apache/shardingsphere/issues/23973#issuecomment-1416645630

   > > Thanks for your report.
   > > 
   > > The root cause of this issue is ShardingSphere didn't implemented the method `getStatement` of `DatabaseMetaDataResultSet`.
   > > 
   > > ```
   > > Caused by: java.sql.SQLFeatureNotSupportedException: getStatement
   > > 	at org.apache.shardingsphere.driver.jdbc.unsupported.AbstractUnsupportedDatabaseMetaDataResultSet.getStatement(AbstractUnsupportedDatabaseMetaDataResultSet.java:92) ~[shardingsphere-jdbc-core-5.3.1.jar:5.3.1]
   > > 	at com.zaxxer.hikari.pool.ProxyDatabaseMetaData.getTables(ProxyDatabaseMetaData.java:69) ~[HikariCP-4.0.3.jar:na]
   > > 	at com.zaxxer.hikari.pool.HikariProxyDatabaseMetaData.getTables(HikariProxyDatabaseMetaData.java) ~[HikariCP-4.0.3.jar:na]
   > > 	at org.hibernate.tool.schema.extract.internal.InformationExtractorJdbcDatabaseMetaDataImpl.processTableResultSet(InformationExtractorJdbcDatabaseMetaDataImpl.java:64) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   > > 	at org.hibernate.tool.schema.extract.internal.AbstractInformationExtractorImpl.getTables(AbstractInformationExtractorImpl.java:565) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   > > 	... 35 common frames omitted
   > > ```
   > 
   > Is that mean there nothing wrong with my configuration, right?
   
   Indeed. This is an framework integration issue.


-- 
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: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] TeslaCN commented on issue #23973: sharding-jdbc 5.3.1: The Rule of ReadWrite-Splitting does not work

Posted by "TeslaCN (via GitHub)" <gi...@apache.org>.
TeslaCN commented on issue #23973:
URL: https://github.com/apache/shardingsphere/issues/23973#issuecomment-1416027769

   Thanks for your report.
   
   The root cause of this issue is ShardingSphere didn't implemented the method `getStatement` of `DatabaseMetaDataResultSet`.
   
   ```
   Caused by: java.sql.SQLFeatureNotSupportedException: getStatement
   	at org.apache.shardingsphere.driver.jdbc.unsupported.AbstractUnsupportedDatabaseMetaDataResultSet.getStatement(AbstractUnsupportedDatabaseMetaDataResultSet.java:92) ~[shardingsphere-jdbc-core-5.3.1.jar:5.3.1]
   	at com.zaxxer.hikari.pool.ProxyDatabaseMetaData.getTables(ProxyDatabaseMetaData.java:69) ~[HikariCP-4.0.3.jar:na]
   	at com.zaxxer.hikari.pool.HikariProxyDatabaseMetaData.getTables(HikariProxyDatabaseMetaData.java) ~[HikariCP-4.0.3.jar:na]
   	at org.hibernate.tool.schema.extract.internal.InformationExtractorJdbcDatabaseMetaDataImpl.processTableResultSet(InformationExtractorJdbcDatabaseMetaDataImpl.java:64) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   	at org.hibernate.tool.schema.extract.internal.AbstractInformationExtractorImpl.getTables(AbstractInformationExtractorImpl.java:565) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final]
   	... 35 common frames omitted
   ```


-- 
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: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org