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

Support the autoIndexId option for capped collections #3922

Open
b1ron opened this issue Jan 2, 2024 · 2 comments
Open

Support the autoIndexId option for capped collections #3922

b1ron opened this issue Jan 2, 2024 · 2 comments
Labels
code/feature Some user-visible feature is not implemented yet not ready Issues that are not ready to be worked on; PRs that should skip CI

Comments

@b1ron
Copy link
Contributor

b1ron commented Jan 2, 2024

What should be done?

The autoIndexId option prevents the _id index from being created automatically. When used with non-capped collections the command returns a soon-to-be deprecated note. The option is also not allowed for collections that can be replicated, i.e. created on a DB other than local.

@b1ron b1ron added code/feature Some user-visible feature is not implemented yet not ready Issues that are not ready to be worked on; PRs that should skip CI labels Jan 2, 2024
@AlekSi
Copy link
Member

AlekSi commented Jan 12, 2024

I wonder if we need to implement that at all and why. Does something require it?

@b1ron
Copy link
Contributor Author

b1ron commented Jan 16, 2024

@AlekSi see test that requires it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code/feature Some user-visible feature is not implemented yet not ready Issues that are not ready to be worked on; PRs that should skip CI
Projects
None yet
Development

No branches or pull requests

3 participants