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 2016/01/27 16:05:39 UTC
[jira] [Updated] (AMBARI-14812) Alerts API Does Not Honor JPA
Sorting
[ https://issues.apache.org/jira/browse/AMBARI-14812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hurley updated AMBARI-14812:
-------------------------------------
Attachment: AMBARI-14812.patch
> 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)