Done
Details
Assignee
Sourabh SourabhSourabh SourabhReporter
Sourabh SourabhSourabh SourabhLabels
Components
Fix versions
Affects versions
Priority
Medium
Details
Details
Assignee
Sourabh Sourabh
Sourabh SourabhReporter
Sourabh Sourabh
Sourabh SourabhLabels
Components
Fix versions
Affects versions
Priority
Created October 5, 2022 at 5:25 PM
Updated April 25, 2023 at 11:31 AM
Resolved October 26, 2022 at 1:58 PM
Grooming update :
Module X declare Container A, child container B
Module X imports Module Y
Module Y declares Container C, child container D
A
+B
+C
+D
XPath without prefix /A/B/C/D
Our current solution, only adds very first Module Prefix: X:A/B/C/D but in a very inefficient manner
Future (proper) solution should had at each module chance a prefix: X:A/B/Y:C/D
Scope of bug-fix: Fix the performance issue by decouple the SQL-Query for all fragments form the implementation to get the prefix for the TOP level Fragment
A/C
Functionality unchanged, see scenarios 1 & 2 below
De-coupling can only be checked as code-review
Out of scope
Insertion of prefix for different modules (separate: Jira CPS-1301)
Scenario 1. get for actual top-level container (with children). Note the insertoint of 'stores:' prefix (only for bookstore)
Scenario 2. get for any child-container (with children). Note the insertion of 'stores:' prefix (only for 'inventory')