Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document how to use buckets #26

Open
nirvdrum opened this issue Apr 12, 2023 · 3 comments
Open

Document how to use buckets #26

nirvdrum opened this issue Apr 12, 2023 · 3 comments

Comments

@nirvdrum
Copy link

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?

@bhargavgohil25
Copy link

Yeah. It would be really helpful to include lexorank bucket documentation.

@RishiSargar
Copy link

Yes, It would really helpful get more information on how to apply rebalancing with the help of buckets

@episage
Copy link

episage commented Dec 21, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants