[MGNLUI-3211] HierarchicalJcrContainer performance: child presence resolution is not optimal. Created: 20/Oct/14  Updated: 05/Dec/14  Resolved: 21/Oct/14

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: 5.2.11, 5.3.5

Type: Bug Priority: Critical
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

HierarchicalJcrContainer#hasChildren method internally calls an expensive HierarchicalJcrContainer#getChildren which results in numerous JCR accesses and when operating the tree with massive amount of sibling nodes.

Instead the internal implementation could return true upon the first possible child node is resolved.


Generated at Mon Feb 12 09:04:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.