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

Fix: retrieving migration uuid early in the export schema phase #2128

Merged
merged 2 commits into from
Dec 27, 2024

Conversation

priyanshi-yb
Copy link
Contributor

@priyanshi-yb priyanshi-yb commented Dec 27, 2024

Describe the changes in this pull request

fixes #2127

Describe if there are any user-facing changes

N/A

How was this pull request tested?

Does your PR have changes that can cause upgrade issues?

Component Breaking changes?
MetaDB No
Name registry json No
Data File Descriptor Json No
Export Snapshot Status Json No
Import Data State No
Export Status Json No
Data .sql files of tables No
Export and import data queue No
Schema Dump No
AssessmentDB No
Sizing DB No
Migration Assessment Report Json No
Callhome Json No
YugabyteD Tables No
TargetDB Metadata Tables No

@priyanshi-yb priyanshi-yb marked this pull request as ready for review December 27, 2024 14:59
@priyanshi-yb priyanshi-yb merged commit a85c6fc into main Dec 27, 2024
67 checks passed
@priyanshi-yb priyanshi-yb deleted the priyanshi/fix-export-schema-uuid branch December 27, 2024 15:00
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

Successfully merging this pull request may close these issues.

in export-schema, generate migration UUID early to avoid 0000-0000-... uuid being sent to call-home.
2 participants