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

store: Fix change_health_column migration for sharded setup #5183

Merged
merged 1 commit into from
Jan 31, 2024

Conversation

lutter
Copy link
Collaborator

@lutter lutter commented Jan 31, 2024

No description provided.

@lutter lutter requested a review from zorancv January 31, 2024 20:03
execute 'drop foreign table ' || r.nsp || '.subgraph_deployment';
end loop;
end
$$;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we need to do the same in the down migration too.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I looked at the down migration, and I think that is fine, since when we run the down migration, the imported tables don't reference anything.

Copy link
Contributor

@zorancv zorancv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to me

@lutter
Copy link
Collaborator Author

lutter commented Jan 31, 2024

On my local test system, I had to manually run graphman database remap to rebuild the table imports. It's not clear why that is, but I think it's in one of my shards the migration failed because of a local change I had that shouldn't have been there.

@lutter lutter merged commit 6067090 into master Jan 31, 2024
7 checks passed
@lutter lutter deleted the lutter/health branch January 31, 2024 20:51
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.

None yet

2 participants