[
https://issues.apache.org/jira/browse/AMBARI-14812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15120377#comment-15120377
]
Hudson commented on AMBARI-14812:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #4237 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4237/])
AMBARI-14812 - Alerts API Does Not Honor JPA Sorting (jonathanhurley) (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=73b5399b12b4c17c119d37031d8e92ca398ca195])
*
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertsDAOTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertDefinitionResourceProvider.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertResourceProvider.java
> 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)
