[GitHub] cherrylzhao opened a new issue #1957: autogen key sharding-column can't be routed succeed while using default sharding strategy

[GitBox <gi...@apache.org>]

cherrylzhao opened a new issue #1957: autogen key sharding-column can't be routed succeed while using default sharding strategy
URL: https://github.com/apache/incubator-shardingsphere/issues/1957
 
 
   ## Bug Report
   
   ### Which version of ShardingSphere did you use?
   4.0.0.M1-SNAPSHOT
   
   ### Which project did you use? Sharding-JDBC or Sharding-Proxy?
   Sharding-JDBC
   
   ### Expected behavior
   order_id use SNOWFLAKE algorithm, which is the table sharding-colum.
   `INSERT INTO t_order (user_id, status) VALUES (?, ?) ` should be routed to
   t_order_0 or t_order_1
   
   ### Actual behavior
   route to t_order_0 and t_order_1
   
   ### Reason analyze (If you can)
   OptimizeEngine haven't make autogen sharding-column as `ShardingCondition`
   
   ### Example codes for reproduce this issue (such as a github link).
   following unit test case of sharding-example project.
   `io.shardingsphere.example.jdbc.nodep.JavaConfigurationExampleTest#assertShardingTables`
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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


With regards,
Apache Git Services