I saw that Bigtop 0.7.0 was just released, would I break anything in Ambari 1.2.5 if I pulled HBase bits using bigtop repo?
From: Artem Ervits [mailto:[email protected]] Sent: Tuesday, November 05, 2013 10:12 AM To: [email protected] Subject: RE: upgrade Ambari-provisioned HBase cluster Anyone? From: Artem Ervits [mailto:[email protected]]<mailto:[mailto:[email protected]]> Sent: Monday, November 04, 2013 5:33 PM To: [email protected]<mailto:[email protected]> Subject: upgrade Ambari-provisioned HBase cluster Hello all, My current cluster is Ambari 1.2.5 HBase 0.94.5.3 Hadoop 1.1.2 I'd like to upgrade HBase to 0.94.12, what are some of the approaches that I can follow to do that? 1. Wait for next stack release (maybe a problem because we're not ready to go with Hadoop 2) 2. Compile my own rpms and deploy Can anyone suggest a good approach that won't break compatibility with future Ambari release? Same applies to Hadoop, if I wanted to upgrade to 1.2.1 Thank you Artem Ervits [email protected]<mailto:[email protected]> New York Presbyterian Hospital This electronic message is intended to be for the use only of the named recipient, and may contain information that is confidential or privileged. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message. Thank you. ________________________________ Confidential Information subject to NYP's (and its affiliates') information management and security policies (http://infonet.nyp.org/QA/HospitalManual). This electronic message is intended to be for the use only of the named recipient, and may contain information that is confidential or privileged. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message. Thank you. ________________________________ Confidential Information subject to NYP's (and its affiliates') information management and security policies (http://infonet.nyp.org/QA/HospitalManual). This electronic message is intended to be for the use only of the named recipient, and may contain information that is confidential or privileged. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message. Thank you.
