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

Allow option to specific CREATE INDEX to be CONCURRENTLY or NONCONCURRENTLY for target database YugabyteDB #1382

Closed
ssherwood opened this issue Mar 25, 2024 · 2 comments

Comments

@ssherwood
Copy link

ssherwood commented Mar 25, 2024

Jira Link: DB-13446
YugabyteDB defaults index creation to CONCURRENTLY. This is most appropriate for on-line (live) migrations. However, for offline migrations, it may be desirable to have YugabyteDB use NONCONCURRENTLY instead.

This should be an optional configuration option when generating the CREATE INDEX output for YugabyteDB.

@hbhanawat
Copy link
Collaborator

@makalaaneesh is this issue still relevant?

@hbhanawat hbhanawat removed the triage Needs to be triaged label Oct 24, 2024
@makalaaneesh
Copy link
Collaborator

With voyager 1.7.2, we changed the workflows to import indexes in the import schema step as opposed to import-schema --post-snapshot-import true step.

With this change, the indexes will be created at at time when there is no data present in the tables. Therefore, having the ability to create indexes NON-CONCURRENTLY is not relevant anymore.

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

No branches or pull requests

5 participants