Re-index subtree on move #223
Open
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
|
should this be made optional via an ini setting? normally a content in Solr does not carry info about all its grandparents... or does it ? |
|
@gggeek The node path is in the index, right? So solr searches using the node path will return funny results. +1 |
|
Correct, there is at least path and visibility information to update, so I don't think this should be optional. |
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.
Currently, eZ Find does not re-index a node's subtree when the node is moved. This PR uses the same strategy that we use when the node's visibility is toggled, which is to defer the re-index to the ezfindindexsubtree cronjob.