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.

Sign up for GitHub

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

Add bit reverse example to dev-guide-unique-serial-number-generation (#15748) #15784

Merged
merged 3 commits into from
Dec 19, 2023
Merged

Add bit reverse example to dev-guide-unique-serial-number-generation (#15748) #15784

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9abed74
Add bit reverse example to dev-guide-unique-serial-number-generation.md
Tetsuya3850 Dec 17, 2023
cd67b84
Update develop/dev-guide-unique-serial-number-generation.md
Tetsuya3850 Dec 18, 2023
f6349cd
make jenkins happy
Oreoxmt Dec 18, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion develop/dev-guide-unique-serial-number-generation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,4 +48,4 @@ The number allocation solution can be understood as bulk acquisition of auto-inc

Every time, the application gets a segment of sequence numbers at the configured step. It updates the database at the same time to persist the maximum value of the current sequence that has been allocated. The processing and allocation of sequence numbers are completed in the application's memory. After a segment of sequence numbers is used up, the application gets a new segment of sequence numbers, which effectively alleviates the pressure on the database write. In practice, you can also adjust the step to control the frequency of database updates.

Finally, note that the IDs generated by the above two solutions are not random enough to be directly used as **primary keys** for TiDB tables. In practice, you can perform bit-reverse on the generated IDs to get more random new IDs.
Finally, note that the IDs generated by the above two solutions are not random enough to be directly used as **primary keys** for TiDB tables. In practice, you can perform bit-reverse on the generated IDs to get more random new IDs. For example, after performing bit-reverse, the ID `00000010100101000001111010011100` becomes `00111001011110000010100101000000`, and `11111111111111111111111111111101` becomes `10111111111111111111111111111111`.
Loading