You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've gone through the logic quite a few times and I can't figure why trySplit() (splitting of cell range into multiple) is needed.
Can't I just take the lowest minimum range of all the cells, and the highest maximum range of all the cells, and construct a DDB BETWEEN condition on the local secondary index?
For example, if my covering had 3 cells and I have a hashKeyLength of 3:
When generating the queries to dispatch to DDB, this library goes through all the cells in a covering area, and splits the low and hi range of each cell into sub-ranges based on the hash key length.
I've gone through the logic quite a few times and I can't figure why trySplit() (splitting of cell range into multiple) is needed.
Can't I just take the lowest minimum range of all the cells, and the highest maximum range of all the cells, and construct a DDB
BETWEEN
condition on the local secondary index?For example, if my covering had 3 cells and I have a hashKeyLength of 3:
Can't I just do
BETWEEN
123456789
and125678912
?Why do I have to
trySplit()
cell1
s range (123456789-123999999
) into 3 separate ranges?The text was updated successfully, but these errors were encountered: