EZP-31478: Dropped LSE FullText index from clean data #2984
Conversation
This file contains 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
alongosz
requested review from
adamwojs,
michal-myszka,
mikadamczyk,
Nattfarinn,
ViniTou and
webhdx
adamwojs
approved these changes
Mar 12, 2020
alongosz
force-pushed
the
ezp-31478-drop-lse-fulltext-index-from-cleandata
branch
from
f8f8c2c to
90f049c
Compare
ViniTou
approved these changes
Mar 13, 2020
6 tasks
katarzynazawada
approved these changes
Mar 16, 2020
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.
master (8.0@dev)for eZ Platformv3.0Since eZ Platform
v1.9theezplatform:reindexSymfony command re-indexes all Content items after installation (ezplatform:install). Having Legacy Search Engine FullText index data in initial data (a.k.acleandata.sql) is both redundant and obsolete, since it might be outdated anyway.Moreover since eZ Platform
v2.5.6, theezplatform:installcommand accepts --skip-indexing option, so this even could be seen as a bug. The bug is not visible by accident due to changes from #2940 released in eZ Platformv2.5.9, so there's no point in fixing it for7.5branch.QA
Make sure the search engine set is
legacy. Does not affect Solr.ezplatform:installwithout--skip-indexingoption.ezplatform:installwith--skip-indexingoption. AdminUI search should not return any results untilezplatform:reindexis called. Optionally, If you want to observe the change in behavior, you could switch to thev3.0.0-beta5tag or anything older.TODO: