Repository navigation
chore: merge main back into dev after the long summary hotfix - #286
Merged
Merged
Conversation
Use case and collaborative summaries can be up to 200,000 characters, but their search mapping kept a keyword-analyzed raw copy that turns the whole value into one token, and Elasticsearch rejects tokens over 32,766 bytes. Saving a published item with a long summary returned an error. Removes those raw sub-fields from the long text fields of all search documents (same change as #278 and #281 on dev) and adds migration 0054, which drops and recreates any live index still carrying one; the deploy then refills it. Fixes #266
Adds migration 0065 joining main's 0054_rebuild_long_text_search_indexes with dev's 0064, so dev to main releases keep a single migration leaf.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Follow-up to #283.
Main got migration
0054_rebuild_long_text_search_indexeson its own (main wasat 0053), while dev already has 0054–0064. This brings main into dev and adds
0065_merge_search_hotfix, which depends on both, so there is one migrationleaf and the next dev to main release can migrate.
0054–0064 run (0064 does nothing), then 0065.
Must be merged before any dev to main release (e.g. #279).