[
https://issues.apache.org/jira/browse/AMBARI-7196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14125462#comment-14125462
]
Hudson commented on AMBARI-7196:
--------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #167 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/167/])
AMBARI-7196 Config history table pagination strange behavior. (atkach) (atkach:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8b26d8b0b215d3d8385a4051a070ddc6b2752e3f)
* ambari-web/app/views/main/dashboard/config_history_view.js
* ambari-web/app/controllers/main/dashboard/config_history_controller.js
* ambari-web/app/mixins/common/table_server_mixin.js
> 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)
