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 2020/04/30 02:26:16 UTC

[GitHub] [shardingsphere] henrypoter opened a new issue #5389: sharding-scaling getTableNames error

henrypoter opened a new issue #5389:
URL: https://github.com/apache/shardingsphere/issues/5389


   ## Bug Report
   
   ### Which version of ShardingSphere did you use?
   4.1.0
   ### Which project did you use? Sharding-JDBC or Sharding-Proxy?
   sharding-scaling
   
   ### Expected behavior
   I have a table, it's primary key's type is bigint.
   when the scaling fetch the primary key range, it use rs.getInt() rather than rs.getLong(),  which cause  Integer overflow.
   Proof:
   org.apache.shardingsphere.shardingscaling.core.synctask.history.HistoryDataSyncTaskGroup line 141-142
   
   ### Actual behavior
   
   ### Reason analyze (If you can)
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
   when the primary key's value is bigger than Integer.MAX
   
   


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

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