> On May 3, 2016, 2:33 p.m., Jonathan Hurley wrote: > > The upgrade catalog stuff will be in a separate Jira?
Yes. - Nahappan ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/46545/#review131562 ----------------------------------------------------------- On May 3, 2016, 1:09 p.m., Nahappan Somasundaram wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/46545/ > ----------------------------------------------------------- > > (Updated May 3, 2016, 1:09 p.m.) > > > Review request for Ambari, Alejandro Fernandez, Ajit Kumar, Jonathan Hurley, > Jayush Luniya, and Sumit Mohanty. > > > Bugs: AMBARI-16029 > https://issues.apache.org/jira/browse/AMBARI-16029 > > > Repository: ambari > > > Description > ------- > > AMBARI-16029: Ambari version history - Create DB table, constraints and > sequence id. > > ** Issue ** > In order to support tracking of ambari version, a DB table is required. > > ** Fix ** > Create ambari_operation_history table to store from version, to version, > install type, start and stop timestamps. > > > Diffs > ----- > > ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql > 319afa579e6f5090588fb90fe619ee7b6bae6d78 > ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql > 9a20b8c05801f61a91a092afd4424173a94d7f17 > ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql > e1da7190d6fb929277c834b29cb537107d857bc3 > ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql > ab1eec42fcba467e0bae19674a7877c79eb77b8e > ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql > bd869f454ae7ec1c84a9cbd418875f10c023a0c2 > ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql > fdba489f2d0759e9c1282dfad38036f9bce3673d > ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql > a1da8e5c8343ae554b4e95717cda085c7f79bc46 > > Diff: https://reviews.apache.org/r/46545/diff/ > > > Testing > ------- > > ** 1. mvn clean install ** > > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] Ambari Main ....................................... SUCCESS [11.109s] > [INFO] Apache Ambari Project POM ......................... SUCCESS [0.037s] > [INFO] Ambari Web ........................................ SUCCESS [32.312s] > [INFO] Ambari Views ...................................... SUCCESS [1.275s] > [INFO] Ambari Admin View ................................. SUCCESS [8.752s] > [INFO] ambari-metrics .................................... SUCCESS [0.375s] > [INFO] Ambari Metrics Common ............................. SUCCESS [0.521s] > [INFO] Ambari Metrics Hadoop Sink ........................ SUCCESS [1.184s] > [INFO] Ambari Metrics Flume Sink ......................... SUCCESS [0.616s] > [INFO] Ambari Metrics Kafka Sink ......................... SUCCESS [0.678s] > [INFO] Ambari Metrics Storm Sink ......................... SUCCESS [2.215s] > [INFO] Ambari Metrics Collector .......................... SUCCESS [8.408s] > [INFO] Ambari Metrics Monitor ............................ SUCCESS [2.389s] > [INFO] Ambari Metrics Grafana ............................ SUCCESS [1.170s] > [INFO] Ambari Metrics Assembly ........................... SUCCESS [1:21.702s] > [INFO] Ambari Server ..................................... SUCCESS [3:40.188s] > [INFO] Ambari Functional Tests ........................... SUCCESS [3.530s] > [INFO] Ambari Agent ...................................... SUCCESS [30.377s] > [INFO] Ambari Client ..................................... SUCCESS [0.106s] > [INFO] Ambari Python Client .............................. SUCCESS [1.418s] > [INFO] Ambari Groovy Client .............................. SUCCESS [2.914s] > [INFO] Ambari Shell ...................................... SUCCESS [0.077s] > [INFO] Ambari Python Shell ............................... SUCCESS [1.011s] > [INFO] Ambari Groovy Shell ............................... SUCCESS [1.401s] > [INFO] ambari-logsearch .................................. SUCCESS [0.329s] > [INFO] Ambari Logsearch Appender ......................... SUCCESS [0.377s] > [INFO] Ambari Logsearch Portal ........................... SUCCESS [8.035s] > [INFO] Ambari Logsearch Log Feeder ....................... SUCCESS [2.534s] > [INFO] Ambari Logsearch Solr Client ...................... SUCCESS [0.906s] > [INFO] Ambari Logsearch Assembly ......................... SUCCESS [0.150s] > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD SUCCESS > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 7:08.197s > [INFO] Finished at: Tue May 03 13:06:54 PDT 2016 > [INFO] Final Memory: 281M/1172M > [INFO] > ------------------------------------------------------------------------ > > > ** 2. Manual testing ** > Tested with Ambari-DDL-Postgres-EMBEDDED-CREATE.sql. Copied the SQL script to > a VM and ran ambari-server reset. Verified the schema: > > ambari=> \d+ ambari_operation_history > Table "ambari.ambari_operation_history" > Column | Type | Modifiers | Storage | Description > ----------------+------------------------+-----------+----------+------------- > id | bigint | not null | plain | > from_version | character varying(255) | not null | extended | > to_version | character varying(255) | not null | extended | > start_time | bigint | not null | plain | > end_time | bigint | | plain | > operation_type | character varying(255) | not null | extended | > comments | text | | extended | > Indexes: > "pk_ambari_operation_history" PRIMARY KEY, btree (id) > Has OIDs: no > > > Thanks, > > Nahappan Somasundaram > >
