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

Actually add full text indexes when processing schema changes that require them #6823

Merged
merged 5 commits into from
Jul 25, 2023

Conversation

jbreams
Copy link
Contributor

@jbreams jbreams commented Jul 24, 2023

What, How & Why?

This makes processing additive schema changes where one of the changes is adding a full-text search index actually add the full text search index. Without this change synchronized realms opened asynchronously could end up without any of their defined full text search indexes created and full text searches throwing an error with the message Column has no fulltext index.

☑️ ToDos

  • 📝 Changelog update
  • 🚦 Tests (or not relevant)
  • C-API, if public C++ API changed.

@@ -633,7 +634,16 @@ static void create_initial_tables(Group& group, std::vector<SchemaChange> const&
}
void operator()(AddIndex op)
{
add_search_index(table(op.object), *op.property, op.type);
switch (op.type) {
Copy link
Member

Choose a reason for hiding this comment

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

This should presumably be in add_search_index() rather than duplicating it in each of the cases?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

add_search_index actually already did the right thing and we just weren't calling it right in the additive schema change case.

@jbreams jbreams requested a review from tgoyne July 24, 2023 22:21
@jbreams jbreams marked this pull request as ready for review July 24, 2023 22:21
@jbreams jbreams merged commit 5e87cf3 into master Jul 25, 2023
@jbreams jbreams deleted the jbr/fix_full_text_with_sync branch July 25, 2023 00:33
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants