PROBLEM DESCRIPTION

The focus of this epic is the search framework.  Data modeling and performance aspects will be handled under separate epics. 

The limitations in the search framework make some of the sorting and searching capabilities we are want to provide difficult to impossible.  This epic will focus on those issues such as the "4-way sort" VM 2.0 wants to accomplish and other parts of search that may benefit from left outer joins, etc.  

During the VM 2.0 initiative implementation as well as Compliance 2.0 implementation it's been discovered that existing postgres schema  and associated search framework has a lot of limitations as a result of which: 

• we are unable to sort certain columns due to performance concerns and 
• for corner cases ACS is in a jeopardy of providing inaccurate results or can have data discrepancies

These concerns have been documented in: 

• ROX-24134: Scan Data Discrepancies; Research document 
• ROX-17252: [Workload CVE GA] Resolve image-cve edge search issue

Concerns: 

• Data inaccuracies
• Data discrepancies 
• UX performance around data sorting 

The underlying issues, if not addressed sooner can have a massive negative impact on two main use-cases in ACS and widely used by ACS customers: 

• Vulnerability management 
• Compliance