You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Aleksandr Kovalenko (JIRA)" <ji...@apache.org> on 2014/09/08 14:03:28 UTC
[jira] [Commented] (AMBARI-7196) Config history table pagination
strange behavior
[ https://issues.apache.org/jira/browse/AMBARI-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14125433#comment-14125433 ]
Aleksandr Kovalenko commented on AMBARI-7196:
---------------------------------------------
+1 for the patch
> Config history table pagination strange behavior
> ------------------------------------------------
>
> Key: AMBARI-7196
> URL: https://issues.apache.org/jira/browse/AMBARI-7196
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 1.7.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Fix For: 1.7.0
>
> Attachments: AMBARI-7196.patch
>
>
> Navigate to Dashboard->Config History.
> Check items per page is set to 10.
> Also need to have more then 10 table items to have second page.
> navigate to second page using 'next page' button (blue right arrow)
> Then navigate somewhere from config history page (For example navigate to ZooKeeper service page).
> Again navigate to Dashboard->Config History.
> Table shows first page with 10 items.
> Wait for 10 seconds.
> Page itself switches to second page.
> Probably this is wrong, table should show first page, not page last viewed.
> Or it should immediately navigate to last viewed page, not after 10 seconds delay.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)