> On June 20, 2015, 2:59 p.m., Sumit Mohanty wrote:
> > ambari-server/src/main/package/deb/control/preinst, line 55
> > <https://reviews.apache.org/r/35691/diff/1/?file=988882#file988882line55>
> >
> >     If I understand correctly, this is copying the jars to the backup 
> > folder. However, the title says  that the archives to be left in place. Is 
> > there a post install logic already to copy the jars back to the original 
> > folder?
> 
> Dmitro Lisnichenko wrote:
>     we introduce "backup" folder 
> /var/lib/ambari-server/resources/views/backups and copy jars to that folder. 
> No renaming, removing on upgrade....and well clear, about type of that folder.

Got it, thanks. Let's change the title of the JIRA to reflect the goal.


- Sumit


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/35691/#review88644
-----------------------------------------------------------


On June 20, 2015, 2:45 p.m., Dmitro Lisnichenko wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/35691/
> -----------------------------------------------------------
> 
> (Updated June 20, 2015, 2:45 p.m.)
> 
> 
> Review request for Ambari and Myroslav Papirkovskyy.
> 
> 
> Bugs: AMBARI-12044
>     https://issues.apache.org/jira/browse/AMBARI-12044
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> Installed Ambari 2.0.1, then performed upgrade to Ambari 2.1.0 and the 
> existing view archives got deleted. The view archives that were installed 
> with ambari 2.0.1 (jobs, slider and tez) should have stayed in place. The 
> work directories were still in place but the archives are gone.
> 
> 
> Diffs
> -----
> 
>   ambari-server/src/main/package/deb/control/preinst fdf0372 
>   ambari-server/src/main/package/rpm/preinstall.sh 6db7481 
> 
> Diff: https://reviews.apache.org/r/35691/diff/
> 
> 
> Testing
> -------
> 
> manual check
> 
> 
> Thanks,
> 
> Dmitro Lisnichenko
> 
>

Reply via email to