[GitHub] [shardingsphere] strongduanmu commented on issue #12293: VOLUME_RANGE sharding strategy exception in sharding-5-beata.

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

strongduanmu commented on issue #12293:
URL: https://github.com/apache/shardingsphere/issues/12293#issuecomment-929868712


   > @qiuxiaotong2021 I saw your properties
   > 
   > ```
   > spring.shardingsphere.rules.sharding.tables.t_order.table-strategy.standard.sharding-column=order_id
   > spring.shardingsphere.rules.sharding.tables.t_order.table-strategy.standard.sharding-algorithm-name=order-volume-range-table
   > spring.shardingsphere.rules.sharding.sharding-algorithms.order-volume-range-table.type=VOLUME_RANGE
   > spring.shardingsphere.rules.sharding.sharding-algorithms.order-volume-range-table.props.range-lower=5
   > spring.shardingsphere.rules.sharding.sharding-algorithms.order-volume-range-table.props.range-upper=10
   > spring.shardingsphere.rules.sharding.sharding-algorithms.order-volume-range-table.props.sharding-volume=5
   > ```
   > 
   > this will make the range to `-∞,5), [5,10),[10,+∞) ` and you sharding key is `order_id` , So it'll sharding to t_order_2 , but it is not exist. Refer to `AbstractRangeShardingAlgorithm`
   
   According to @tuichenchuxin  investigation, it can be seen that there is no problem with the `VOLUME_RANGE` algorithm, so I will close 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