You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2021/12/31 03:28:06 UTC

[GitHub] [shardingsphere] ShootingFun opened a new issue #14453: Runtime exception: [unsupported table: `PROFILING`]

ShootingFun opened a new issue #14453:
URL: https://github.com/apache/shardingsphere/issues/14453


   1. When I insert the logic library, the data can be inserted successfully, and the data source can also desensitize and save the data, but Navicat will prompt "Runtime exception: [unsupported table: `PROFILING`]"
   Output log prompt:
   [ERROR] 2021-12-31 10:58:15.338 [Connection-5-ThreadExecutor] o.a.s.p.f.c.CommandExecutorTask-Exception occur:
   java.lang.UnsupportedOperationException: unsupported table: `PROFILING`
           at org.apache.shardingsphere.proxy.backend.text.admin.mysql.MySQLInformationSchemaExecutorFactory.newInstance(MySQLInformationSchemaExecutorFactory.java:52)
           at org.apache.shardingsphere.proxy.backend.text.admin.mysql.MySQLAdminExecutorFactory.newInstance(MySQLAdminExecutorFactory.java:105)
           at org.apache.shardingsphere.proxy.backend.text.admin.DatabaseAdminBackendHandlerFactory.newInstance(DatabaseAdminBackendHandlerFactory.java:78)
           at org.apache.shardingsphere.proxy.backend.text.TextProtocolBackendHandlerFactory.newInstance(TextProtocolBackendHandlerFactory.java:86)
           at org.apache.shardingsphere.proxy.frontend.mysql.command.query.text.query.MySQLComQueryPacketExecutor.<init>(MySQLComQueryPacketExecutor.java:55)
           at org.apache.shardingsphere.proxy.frontend.mysql.command.MySQLCommandExecutorFactory.newInstance(MySQLCommandExecutorFactory.java:73)
           at org.apache.shardingsphere.proxy.frontend.mysql.command.MySQLCommandExecuteEngine.getCommandExecutor(MySQLCommandExecuteEngine.java:60)
           at org.apache.shardingsphere.proxy.frontend.command.CommandExecutorTask.executeCommand(CommandExecutorTask.java:97)
           at org.apache.shardingsphere.proxy.frontend.command.CommandExecutorTask.run(CommandExecutorTask.java:72)
           at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
           at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
           at java.lang.Thread.run(Unknown Source)
   2. After configuring Sharding-Proxy, a view with the same name as the table will appear in the logic library opened by Navicat, which can be opened, but an exception will be reported after opening that this is not a view.
   Output log prompt:
   [ERROR] 2021-12-31 11:04:09.839 [Connection-7-ThreadExecutor] o.a.s.p.f.c.CommandExecutorTask - Exception occur:
   java.sql.SQLException: 'encrypt_db.t_user' is not VIEW
           at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:127)
           at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:95)
           at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
           at com.mysql.cj.jdbc.StatementImpl.executeInternal(StatementImpl.java:790)
           at com.mysql.cj.jdbc.StatementImpl.execute(StatementImpl.java:808)
           at com.zaxxer.hikari.pool.ProxyStatement.execute(ProxyStatement.java:103)
           at com.zaxxer.hikari.pool.HikariProxyStatement.execute(HikariProxyStatement.java)
           at org.apache.shardingsphere.proxy.backend.communication.jdbc.executor.callback.impl.ProxyStatementExecutorCallback.execute(ProxyStatementExecutorCallback.java:40)
           at org.apache.shardingsphere.proxy.backend.communication.jdbc.executor.callback.ProxyJDBCExecutorCallback.executeSQL(ProxyJDBCExecutorCallback.java:73)
           at org.apache.shardingsphere.proxy.backend.communication.jdbc.executor.callback.ProxyJDBCExecutorCallback.executeSQL(ProxyJDBCExecutorCallback.java:66)
           at org.apache.shardingsphere.proxy.backend.communication.jdbc.executor.callback.ProxyJDBCExecutorCallback.executeSQL(ProxyJDBCExecutorCallback.java:44)
           at org.apache.shardingsphere.infra.executor.sql.execute.engine.driver.jdbc.JDBCExecutorCallback.execute(JDBCExecutorCallback.java:85)
           at org.apache.shardingsphere.infra.executor.sql.execute.engine.driver.jdbc.JDBCExecutorCallback.execute(JDBCExecutorCallback.java:64)
           at org.apache.shardingsphere.infra.executor.kernel.ExecutorEngine.syncExecute(ExecutorEngine.java:101)
           at org.apache.shardingsphere.infra.executor.kernel.ExecutorEngine.parallelExecute(ExecutorEngine.java:97)
           at org.apache.shardingsphere.infra.executor.kernel.ExecutorEngine.execute(ExecutorEngine.java:82)
           at org.apache.shardingsphere.infra.executor.sql.execute.engine.driver.jdbc.JDBCExecutor.execute(JDBCExecutor.java:65)
           at org.apache.shardingsphere.proxy.backend.communication.jdbc.executor.ProxyJDBCExecutor.execute(ProxyJDBCExecutor.java:71)
           at org.apache.shardingsphere.proxy.backend.communication.ProxySQLExecutor.useDriverToExecute(ProxySQLExecutor.java:185)
           at org.apache.shardingsphere.proxy.backend.communication.ProxySQLExecutor.execute(ProxySQLExecutor.java:138)
           at org.apache.shardingsphere.proxy.backend.communication.ProxySQLExecutor.execute(ProxySQLExecutor.java:127)
           at org.apache.shardingsphere.proxy.backend.communication.ProxyLockEngine.doExecute(ProxyLockEngine.java:103)
           at org.apache.shardingsphere.proxy.backend.communication.ProxyLockEngine.execute(ProxyLockEngine.java:81)
           at org.apache.shardingsphere.proxy.backend.communication.DatabaseCommunicationEngine.execute(DatabaseCommunicationEngine.java:126)
           at org.apache.shardingsphere.proxy.backend.text.data.impl.UnicastDatabaseBackendHandler.execute(UnicastDatabaseBackendHandler.java:61)
           at org.apache.shardingsphere.proxy.frontend.mysql.command.query.text.query.MySQLComQueryPacketExecutor.execute(MySQLComQueryPacketExecutor.java:61)
           at org.apache.shardingsphere.proxy.frontend.command.CommandExecutorTask.executeCommand(CommandExecutorTask.java:99)
           at org.apache.shardingsphere.proxy.frontend.command.CommandExecutorTask.run(CommandExecutorTask.java:72)
           at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
           at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
           at java.lang.Thread.run(Unknown Source)
   And the view cannot be deleted
   3. When viewing the object information of the logic library table in Navicat, it will report "Field'Engine' not found" error
   ![Field'Engine' not found](https://user-images.githubusercontent.com/70735189/147801458-181159c7-387b-4ce3-b77c-0645d849a926.png)
   ![unsupported table](https://user-images.githubusercontent.com/70735189/147801463-da61180a-959d-495b-8cbf-252b13e01cae.png)
   ![View](https://user-images.githubusercontent.com/70735189/147801464-53dcb9b7-8099-46bf-a369-3bba834e54ab.png)
   


-- 
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] terrymanu commented on issue #14453: Runtime exception: [unsupported table: `PROFILING`]

Posted by GitBox <gi...@apache.org>.
terrymanu commented on issue #14453:
URL: https://github.com/apache/shardingsphere/issues/14453#issuecomment-1043020854


   Closed because of no response for long time.


-- 
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] terrymanu closed issue #14453: Runtime exception: [unsupported table: `PROFILING`]

Posted by GitBox <gi...@apache.org>.
terrymanu closed issue #14453:
URL: https://github.com/apache/shardingsphere/issues/14453


   


-- 
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] RaigorJiang commented on issue #14453: Runtime exception: [unsupported table: `PROFILING`]

Posted by GitBox <gi...@apache.org>.
RaigorJiang commented on issue #14453:
URL: https://github.com/apache/shardingsphere/issues/14453#issuecomment-1003269706


   Hi @ShootingFun 
   1. Query `PROFILING` is the need for Navicat to display additional information, and does not affect your business SQL
   2. Different versions of Navicat behave differently, the tested version will not pop up a dialog box, and there is no additional view;
   
   Due to the large number of third-party clients, ShardingSphere can only be compatible with some of them:
   Therefore, it is recommended to check the [FAQ](https://shardingsphere.apache.org/document/current/en/reference/faq/#proxy-how-to-use-a-suitable-database-tools-connecting-shardingsphere-proxy) and choose the recommended version.


-- 
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