[OOZIE-3229] [client] [ui] Improved SLA filtering options

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0.0, 4.3.1
• Fix Version/s: 5.1.0
• Component/s: client, ui
• Assignee: Andras Salamon
• Reporter: Andras Piros
• Created: 26/Apr/18 18:14
• Updated: 18/Jan/19 09:02
• Resolved: 24/Sep/18 08:46

Description

Currently we can apply a range of filters on top of V2SLAServlet that can be used in a rich but undocumented set of ways:

• id
• parent_id
• event_status
• app_name
• nominal_start
• nominal_end

Need to refactor V2SLAServlet to feature:

• a richer set of SLAEvent, SLARegistration, and SLASummary filtering based on their attributes
• filter options will always be AND-ed, never OR-ed to each other
• maintain compatibility with the parameter names and behavior used thus far
• remove SLASummaryFilter and refactor SLASummaryGetForFilterJPAExecutor as just another possibility for confusion
• document new functionality with rich use case / example library so that users can leverage

Issue Links

• blocks: OOZIE-3335 Cleanup parseFilter methods
• is blocked by: OOZIE-3160 PriorityDelayQueue put()/take() can cause significant CPU load due to busy waiting
• relates to: OOZIE-3309 Runtime error during /v2/sla filtering for bundle
• relates to: OOZIE-3310 SQL error during /v2/sla filtering
• links to: Review Board