You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jaimin D Jetly (JIRA)" <ji...@apache.org> on 2012/10/10 03:14:02 UTC
[jira] [Created] (AMBARI-840) hitting browser refresh should not
clear present step data that had already been persisted to local DB
Jaimin D Jetly created AMBARI-840:
-------------------------------------
Summary: hitting browser refresh should not clear present step data that had already been persisted to local DB
Key: AMBARI-840
URL: https://issues.apache.org/jira/browse/AMBARI-840
Project: Ambari
Issue Type: Sub-task
Reporter: Jaimin D Jetly
Assignee: Jaimin D Jetly
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMBARI-840) hitting browser refresh should not
clear present step data that had already been persisted to local DB
Posted by "Jaimin D Jetly (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMBARI-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jaimin D Jetly updated AMBARI-840:
----------------------------------
Attachment: AMBARI-840_1.patch
> hitting browser refresh should not clear present step data that had already been persisted to local DB
> ------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-840
> URL: https://issues.apache.org/jira/browse/AMBARI-840
> Project: Ambari
> Issue Type: Sub-task
> Reporter: Jaimin D Jetly
> Assignee: Jaimin D Jetly
> Labels: AMBARI-666
> Attachments: AMBARI-840_1.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMBARI-840) hitting browser refresh should not
clear present step data that had already been persisted to local DB
Posted by "Jaimin D Jetly (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMBARI-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jaimin D Jetly updated AMBARI-840:
----------------------------------
Labels: AMBARI-666 Installer (was: AMBARI-666)
> hitting browser refresh should not clear present step data that had already been persisted to local DB
> ------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-840
> URL: https://issues.apache.org/jira/browse/AMBARI-840
> Project: Ambari
> Issue Type: Sub-task
> Affects Versions: ambari-666
> Reporter: Jaimin D Jetly
> Assignee: Jaimin D Jetly
> Labels: AMBARI-666, Installer
> Fix For: ambari-666
>
> Attachments: AMBARI-840_1.patch, AMBARI-840_2.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMBARI-840) hitting browser refresh should not
clear present step data that had already been persisted to local DB
Posted by "Yusaku Sako (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMBARI-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yusaku Sako updated AMBARI-840:
-------------------------------
Attachment: AMBARI-840_2.patch
Minor clean up and unit test fixes.
> hitting browser refresh should not clear present step data that had already been persisted to local DB
> ------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-840
> URL: https://issues.apache.org/jira/browse/AMBARI-840
> Project: Ambari
> Issue Type: Sub-task
> Affects Versions: ambari-666
> Reporter: Jaimin D Jetly
> Assignee: Jaimin D Jetly
> Labels: AMBARI-666
> Fix For: ambari-666
>
> Attachments: AMBARI-840_1.patch, AMBARI-840_2.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira