Erik, hello. I believe you meant upgrade to 2.2.2 in step 2. So no. It won’t catch up changes since Ambari will see version equal to 2.2.2 and think that DB is already upgraded.
Usually upgrade is idempotent and you can manually change version in db and try to upgrade again, but since you are building from unreleased sources this is not guaranteed to work at all. !!!! Make sure you did take DB backup prior to testing this. Connect to Ambari DB using corresponding cli tool (psql, mysql, sqlplus) or any other tool you like and execute following statement: UPDATE metainfo SET metainfo_value = '2.2.1' WHERE metainfo_key = 'version'; Regards, Myroslav Papirkovskyi 18 квіт. 2016 р. о 12:12 Eirik Thorsnes <[email protected]<mailto:[email protected]>> написав(ла): Hi All, What happens in the following scenario: 1. compile Ambari from git snapshot of an unreleased branch (e.g. 2.2.2) 2. install and upgrade schema in db (from e.g. Ambari 2.1.0 or 2.2.0) 3. changes to the 2.2.2 schema is introduced in the git branch 4. compile Ambari from a new git snapshot of the same branch (2.2.2) 5. install and upgrade (run ambari upgrade command) Will Ambari introduce the new schema changes from step 3. in step 5., or will it see that the version (e.g. 2.2.2) is identical and not do the db migration again? Regards, Eirik Thorsnes -- Eirik Thorsnes
