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
While looking at the source, I noticed that LexoRank.max() returns the max value for the first bucket and not the max value permissible. I thought maybe this was a bug because the library sets up three buckets. However, the library also can't call LexoRank.between() with two LexoRank instances corresponding to different buckets.
I was under the impression buckets were used to expand the range of possible values or possibly to shard values or help out database indices. But, it looks like the only way to get out of BUCKET_0 is to manually create the LexoRank with a reference to another LexoRankBucket. Can you please clarify the role buckets play and how they should be used?
The text was updated successfully, but these errors were encountered:
Buckets are solution to lack of atomic transactions in NoSQL system. You keep using bucket 0 and recreate/rebalance in 1, then switch to using 1. All operations on 0 must be paused while doing it.
While looking at the source, I noticed that
LexoRank.max()
returns the max value for the first bucket and not the max value permissible. I thought maybe this was a bug because the library sets up three buckets. However, the library also can't callLexoRank.between()
with twoLexoRank
instances corresponding to different buckets.I was under the impression buckets were used to expand the range of possible values or possibly to shard values or help out database indices. But, it looks like the only way to get out of
BUCKET_0
is to manually create theLexoRank
with a reference to anotherLexoRankBucket
. Can you please clarify the role buckets play and how they should be used?The text was updated successfully, but these errors were encountered: