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

EZP-31113: Implemented indexing subtree after assigning Section to it #2862

Merged
merged 2 commits into from
Dec 3, 2019

Conversation

kmadejski
Copy link
Member

@kmadejski kmadejski commented Nov 7, 2019

Question Answer
JIRA issue EZP-31113
Bug yes
New feature no
Target version 7.5/master
BC breaks no
Tests pass yes
Doc needed no

AssignSectionToSubtreeSignal is not handled properly in both search implementations as well as in HTTP cache.

Note: These changes will be removed on merge-up and the second PR targeting master will be created.

TODO:

  • Implement feature / fix a bug.
  • Fix new code according to Coding Standards ($ composer fix-cs).
  • Ask for Code Review.
  • Drop changes on merge-up.
  • Create a new PR using events instead (for master).

@kmadejski kmadejski self-assigned this Nov 7, 2019
@kmadejski kmadejski changed the title EZP-31113: AssignSectionToSubtreeSignal is not handled by search and HTTP cache. EZP-31113: AssignSectionToSubtreeSignal is not handled by search and HTTP cache Nov 7, 2019
@adamwojs
Copy link
Member

adamwojs commented Nov 7, 2019

@kmadejski please remember to replace signal/slots with events on master

@kmadejski
Copy link
Member Author

@adamwojs yep, there is even a note in PR, but I'll add it to ToDo list.

Copy link
Member

@alongosz alongosz left a comment

Choose a reason for hiding this comment

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

The PR does not affect HTTP cache, please adjust its title and commits to reflect the actual changes

@kmadejski kmadejski changed the title EZP-31113: AssignSectionToSubtreeSignal is not handled by search and HTTP cache EZP-31113: AssignSectionToSubtreeSignal is not handled by search. Nov 7, 2019
@kmadejski kmadejski changed the title EZP-31113: AssignSectionToSubtreeSignal is not handled by search. EZP-31113: AssignSectionToSubtreeSignal is not handled by search Nov 7, 2019
@kmadejski
Copy link
Member Author

kmadejski commented Nov 7, 2019

The PR does not affect HTTP cache, please adjust its title and commits to reflect the actual changes

@alongosz done in 093cbb2.

@micszo micszo self-assigned this Nov 12, 2019
@alongosz alongosz changed the title EZP-31113: AssignSectionToSubtreeSignal is not handled by search EZP-31113: Implemented indexing subtree after assigning Section to it Nov 12, 2019
Copy link
Member

@micszo micszo left a comment

Choose a reason for hiding this comment

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

Changing section of folder with 5k children (on the same level) causes a timeout. Is it something that can be tweaked with configuration?
The result is that only the children that were handled until the timeout occurred are updated.
Screenshot 2019-11-22 at 15 39 53

@kmadejski
Copy link
Member Author

@micszo no, it's not a matter of configuration. It's due to the implementation of calling Solr. Here you can find a follow-up ticket for it: https://jira.ez.no/browse/EZP-30963. Unfortunately, I didn't have time to take care of it yet.

Copy link
Member

@micszo micszo left a comment

Choose a reason for hiding this comment

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

@micszo micszo removed their assignment Nov 25, 2019
@andrerom
Copy link
Contributor

andrerom commented Dec 3, 2019

Merged to 7.5 and removed when merged up to master.

Also rebased SolrBundle PR and restarted tests on http cache PR, once they are green now they should be ready, but will be handled by @adamwojs as he will look into a few things including event handling for master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

7 participants