Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 369581

Summary: HierarchyIndexColumn class had an inefficient algorithm
Product: [Technology] OSEE Reporter: S. Cook <shawn.f.cook>
Component: Action Tracking System (ATS)Assignee: S. Cook <shawn.f.cook>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: ryan.d.brooks
Version: 0.9.9   
Target Milestone: 0.9.9   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
HierarchyIndexColumn class had an inefficient algorithm ryan.d.brooks: iplog+

Description S. Cook CLA 2012-01-24 14:37:21 EST 
HierarchyIndexColumn class had an inefficient algorithm that, when combined with a large data set (ie: 26,000+), took a very long time to run.  The computeHierarchyIndex() and getPosition() were being used over and over to determine the hierarchy index values.  We made use of a MapMaker - a map that assigns an expiration timer to each item that is added to the map - which acts as a cache and interrupts the horribly inefficient recursive calls.
Comment 1 S. Cook CLA 2012-01-24 14:40:50 EST 
Created attachment 210000 [details]
HierarchyIndexColumn class had an inefficient algorithm