[NIFI-6433] Update getStatusHistory to honor filter parameters

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.9.2
• Fix Version/s: 1.10.0
• Component/s: Core Framework
• Assignee: Mark Owens
• Reporter: Mark Owens
• Created: 11/Jul/19 17:05
• Updated: 31/Jul/19 09:22
• Resolved: 26/Jul/19 15:29

Description

This modification updates the getStatusHistory methods of VolatileComponentStatusRepository to utilize the start, end, and preferredDataPoints parameters when retrieving status histories.

When calling the various getXXXStatusHistory methods of VolatileComponentStatusRepository, they are all passed start, end, and preferredDataPoints values to allow the filtering of histories according to the provided parameters. But the follow-on method calls ignore those values completely. This ticket updates those methods to honor the parameters and filter the returned Dates accordingly.

Although for VolatileComponentStatusRepository the timestamps buffer is rather small, it seems better that the parameters be utilized rather than being silently ignored. This was found during work on a task where I only needed a subset of the buffer returned.

 

Issue Links

• relates to: NIFI-6509 Date related issue in unit test VolatileComponentStatusRepositoryTest
• links to: GitHub Pull Request #3579