You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/07/26 15:28:00 UTC
[jira] [Commented] (NIFI-6433) Update getStatusHistory to honor
filter parameters
[ https://issues.apache.org/jira/browse/NIFI-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16893905#comment-16893905 ]
ASF subversion and git services commented on NIFI-6433:
-------------------------------------------------------
Commit d1c30d14777354de2288b67184ffe9e1ceb98cf1 in nifi's branch refs/heads/master from Mark Owens
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d1c30d1 ]
NIFI-6433 Update getStatusHistory to honor filter values.
This modification updates the getStatusHistory method of
VolatileComponentStatusRepository to utilize the start, end, and
preferredDataPoints parameters when retrieving status histories.
When calling the various get<XXXX>StatusHistory 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.
This closes #3579.
Signed-off-by: Mark Payne <ma...@hotmail.com>
> Update getStatusHistory to honor filter parameters
> --------------------------------------------------
>
> Key: NIFI-6433
> URL: https://issues.apache.org/jira/browse/NIFI-6433
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 1.9.2
> Reporter: Mark Owens
> Assignee: Mark Owens
> Priority: Minor
> Fix For: 1.10.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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.
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)