You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2015/05/29 16:37:18 UTC

[jira] [Updated] (AMBARI-11520) Alert Provider Does Not Return Results Paginated From An Offset

     [ https://issues.apache.org/jira/browse/AMBARI-11520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Hurley updated AMBARI-11520:
-------------------------------------
    Attachment: AMBARI-11520.patch

> Alert Provider Does Not Return Results Paginated From An Offset
> ---------------------------------------------------------------
>
>                 Key: AMBARI-11520
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11520
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11520.patch
>
>
> When requesting the current alerts for a cluster, the following URL returns no results even if there are alerts which would match the pagination criteria:
> {{api/v1/clusters/c1/alerts?fields=*&Alert/state.in(CRITICAL,WARNING)&Alert/maintenance_state.in(OFF)&from=10&page_size=10}}
> However, the following URL does return alerts:
> {{api/v1/clusters/c1/alerts?fields=*&Alert/state.in(CRITICAL,WARNING)&Alert/maintenance_state.in(OFF)&page_size=10}}
> The backend DAO is correctly processing the predicate into a JPA predicate, however the result set is being trimmed in memory before being returned from the query.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)