ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-10052) Current Alerts Requests Should Honor Predicate Values For Performance On Large Cluster
Date Fri, 13 Mar 2015 16:35:38 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-10052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360595#comment-14360595
] 

Hudson commented on AMBARI-10052:
---------------------------------

ABORTED: Integrated in Ambari-branch-2.0.0 #69 (See [https://builds.apache.org/job/Ambari-branch-2.0.0/69/])
AMBARI-10052 - Current Alerts Requests Should Honor Predicate Values For Performance On Large
Cluster (part2) (jonathanhurley) (jhurley: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9f853f0e08e2897b942211ee7d4f7048894c8273)
* ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertCurrentEntity_.java


> Current Alerts Requests Should Honor Predicate Values For Performance On Large Cluster
> --------------------------------------------------------------------------------------
>
>                 Key: AMBARI-10052
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10052
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.0.0
>
>
> When making a request for current alerts, if you want to restrict by an ID, such as the
definition ID, it queries against all entities in the table:
> {{api/v1/clusters/perf400/alerts?fields=*&Alert/definition_id=9}}
> This can cause performance issues in large clusters. We should be using a JPA predicate
here.



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

Mime
View raw message