Open TeslaCN opened 2 years ago
Hello , this issue has not received a reply for several days. This issue is supposed to be closed.
Since this issue has been inactive for a while, I'm closing it.
@TeslaCN Thank you for your feedback, I will check this logic.
Hi @TeslaCN, I took a look at the implementation of the VOLUME_RANGE
algorithm. It is an auto sharding algorithm and is recommended to be used in the auto sharding configuration. Users do not need to care about the underlying actual table.
In addition, because the range sharding algorithm has values outside the boundary, two additional shardings are added to the algorithm to store these values outside the boundary. If we use this algorithm in the standard sharding algorithm, it will indeed be confusing, and I will think about how to optimize it.
Thank you @strongduanmu
Question
My scenario is range sharding.
ID distributes in [1, 32]
Range sharding into 4 data sources: ds_0: [1, 8] ds_1: [9, 16] ds_2: [17, 24] ds_3: [25, 32]
I thought the configuration was:
But the proper configuration is the following:
The properties may confuse users.