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

Jump to bottom

MySQL compatible AUTO_INCREMENT #38442

Closed
tiancaiamao opened this issue Oct 13, 2022 · 2 comments
Closed

MySQL compatible AUTO_INCREMENT #38442

tiancaiamao opened this issue Oct 13, 2022 · 2 comments
Labels
type/feature-request Categorizes issue or PR as related to a new feature.

Comments

@tiancaiamao
Copy link
Contributor

tiancaiamao commented Oct 13, 2022 •
edited
Loading

Feature Request

Is your feature request related to a problem? Please describe:

Currently, TiDB support AUTO_INCREMENT ID that is unique, incremental, but the IDs maybe non-continuous.

For example, where there are two TiDB instance, allocate from instance A get [0-20000),
allocate from instance B get [20000-40000)...
after instance A exhaust its cached IDs, the next allocation get 40000.
The ID sequence looks like: ...19998, 19999, [the hole here], 40000, 40001...

Describe the feature you'd like:

I would like it to be fully MySQL-compatible

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

A centralized auto ID allocating service, so that the AUTO_INCREMENT ID could be unique, incremental, and noncontinuous, just like MySQL.
@tiancaiamao tiancaiamao added the type/feature-request Categorizes issue or PR as related to a new feature. label Oct 13, 2022
@tiancaiamao tiancaiamao mentioned this issue Oct 13, 2022
Closed
12 tasks
This was referenced Oct 28, 2022
Closed
Closed
Merged
Merged
Merged
@tiancaiamao
Copy link
Contributor Author

Split the original PR to make the reviewer's life easier:

@tiancaiamao tiancaiamao mentioned this issue Nov 4, 2022
Merged
12 tasks
@ti-chi-bot ti-chi-bot mentioned this issue Nov 9, 2022
Closed
12 tasks
@sleepymole sleepymole mentioned this issue Nov 10, 2022
Closed
4 tasks
@tiancaiamao tiancaiamao mentioned this issue Dec 1, 2022
Closed
@tiancaiamao tiancaiamao mentioned this issue Jun 16, 2023
Merged
12 tasks
ti-chi-bot bot pushed a commit that referenced this issue Jun 20, 2023
@tiancaiamao
*: fix 'duplicate entry' error when using br to restore AUTO_ID_CACHE…
e0f62ef 
…=1 tables (#44743)

ref #38442, close #44716
This was referenced Jun 20, 2023
Merged
Merged
@dveeden
Copy link
Contributor

dveeden commented Jul 7, 2023

@tiancaiamao can we close this issue?

ti-chi-bot bot pushed a commit that referenced this issue Jul 10, 2023
@ti-chi-bot
*: fix 'duplicate entry' error when using br to restore AUTO_ID_CACHE…
c7f1ee2 
…=1 tables (#44743) (#44817)

ref #38442, close #44716
ti-chi-bot bot pushed a commit that referenced this issue Aug 2, 2023
@ti-chi-bot
*: fix 'duplicate entry' error when using br to restore AUTO_ID_CACHE…
df3fa99 
…=1 tables (#44743) (#44816)

ref #38442, close #44716
ti-chi-bot bot pushed a commit that referenced this issue Sep 22, 2023
@tiancaiamao
docs/design: add MySQL compatible auto_increment design doc (#38807)
241e846 
ref #38442
@tiancaiamao tiancaiamao mentioned this issue Nov 29, 2023
Closed
@tiancaiamao tiancaiamao mentioned this issue Dec 15, 2023
Closed
@tiancaiamao tiancaiamao mentioned this issue May 16, 2024
Merged
13 tasks
ti-chi-bot bot pushed a commit that referenced this issue May 17, 2024
@tiancaiamao
autoid_service: remove the force rebase on close behavior (#53315)
4d6715f 
ref #38442
terry1purcell pushed a commit to terry1purcell/tidb that referenced this issue May 17, 2024
@tiancaiamao @terry1purcell
autoid_service: remove the force rebase on close behavior (pingcap#53315
33d967d 
)

ref pingcap#38442
@ti-chi-bot ti-chi-bot mentioned this issue May 20, 2024
Merged
13 tasks
ti-chi-bot bot pushed a commit that referenced this issue May 20, 2024
@ti-chi-bot
autoid_service: remove the force rebase on close behavior (#53315) (#…
9e5c591 
…53396)

ref #38442
RidRisR pushed a commit to RidRisR/tidb that referenced this issue May 23, 2024
@tiancaiamao @RidRisR
autoid_service: remove the force rebase on close behavior (pingcap#53315
8c0f7e6 
)

ref pingcap#38442
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/feature-request Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

*: support MySQL compatible AUTO_INCREMENT tiancaiamao/tidb
2 participants
@dveeden @tiancaiamao