`is_upgrade` have used before, when we have installed packages using asterisk and packages had same names in different stacks. So when we have moved to newer stack, installation supposed to be forced, even if such package have existed. For 2-3 years already, we using conventional package naming, which supply different package name for each build. This open possibility to not force re-installation of packages if they have already installed.
However, `action_force` still allow 3d-part stack developers to use previous behavior if it intended by their conventions. [ Full content available at: https://github.com/apache/ambari/pull/2366 ] This message was relayed via gitbox.apache.org for [email protected]
