ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yurii Shylov" <yurii.shy...@gmail.com>
Subject Re: Review Request 30568: [PREVIEW] Rolling Upgrade Bootstrap - Allow Ambari upgrade from 1.7.0 - 2.0.0 to populate new tables
Date Wed, 04 Feb 2015 18:24:51 GMT

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

(Updated Фев. 4, 2015, 6:24 п.п.)


Review request for Ambari, Alejandro Fernandez, Dmitro Lisnichenko, and Nate Cole.


Changes
-------

Refactored to use AmbariCustomCommandExecutionHelper for calling save_component_version_to_structured_out


Bugs: AMBARI-9054
    https://issues.apache.org/jira/browse/AMBARI-9054


Repository: ambari


Description
-------

Current implementation schedules request to every component to get its version after server
upgrade 1.7.0 - 2.0.0 was completed. It creates a stage per every component and thus looks
ugly. I'm in the process of rewriting it to use AmbariCustomCommandExecutionHelper to call
save_component_version_to_structured_out() directly for every component.


Diffs (updated)
-----

  ambari-common/src/main/python/resource_management/libraries/script/script.py 683397a 
  ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java
b8f3cd7 
  ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UserResourceProvider.java
35f9db5 
  ambari-server/src/main/java/org/apache/ambari/server/metadata/ActionMetadata.java 8a9799d

  ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog200.java a83d26d


Diff: https://reviews.apache.org/r/30568/diff/


Testing
-------

preview


Thanks,

Yurii Shylov


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message