[
https://issues.apache.org/jira/browse/AMBARI-14812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15120271#comment-15120271
]
Hadoop QA commented on AMBARI-14812:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12784656/AMBARI-14812.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5083//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5083//console
This message is automatically generated.
> Alerts API Does Not Honor JPA Sorting
> -------------------------------------
>
> Key: AMBARI-14812
> URL: https://issues.apache.org/jira/browse/AMBARI-14812
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Fix For: 2.2.2
>
> Attachments: AMBARI-14812.patch
>
>
> Sorted API requests to the alerts endpoint results in data which is not
> sorted at all. Consider this query:
> http://localhost:8080/api/v1/clusters/c1/alerts?fields=Alert/latest_timestamp&sortBy=Alert/latest_timestamp
> The data is returned out of order. This is because the JPA sort is being
> placed into a {{HashSet}} instead of a {{LinkedHashSet}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
