691: Fixing configuration of the 'search_api_db_mukurtu_browse_auto_index' Search API index to use fewer full text fields. #710
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #691
This seems to fix installation issues with the
search_api_db_mukurtu_browse_auto_index
Search API index.This index seemed to be configured almost exactly opposite the way it should be, with 16 fields that are UUIDs being "Fulltext" instead of "String", and the Taxonomy label being "String" instead of "Fulltext". This PR brings this index in line with the other indexes, using strings for UUIDs. By reducing the amount of data in a table, this seems to resolve the installation issues.