Hey Shaofeng， long time no see ☺ Good to hear back from you so soon , thanks !
From the cloudera doc, CDH 5.7 and CDH 5.8 both package the same version of HBase 1.2.0. So I guess it might be ok to go with 5.8 directly. Do you think it’s risky to do so ? Thanks. Fei Jia(费伽) Yum! China, IT 021-24078997 发件人: ShaoFeng Shi [mailto:[email protected]] 发送时间: 2016年8月5日 14:10 收件人: [email protected]; [email protected] 主题: Re: Is Kylin 1.5.3 compatible with CDH 5.8 ? Hi Jia， how are you? CDH 5.8 is a new release that we haven't tested yet; but CDH 5.7 is verified good for kylin 1.5.3. Suggest you use 5.7 if possible. Regards， Shaofeng Shi [email protected]<mailto:[email protected]> From Outlook Mobile<https://aka.ms/qtex0l> _____________________________ From: Fei, Jia <[email protected]<mailto:[email protected]>> Sent: 星期五, 八月 5, 2016 11:18 上午 Subject: Is Kylin 1.5.3 compatible with CDH 5.8 ? To: <[email protected]<mailto:[email protected]>> Hi all, Is Kylin 1.5.3 compatible with CDH 5.8 ? We have a production CDH 5.5.1 (With HBase 1.0.0) , after I installed Kylin 1.5.3 and it turned out it’s not compatible with HBase 1.0.0. The model building can be successfully completed, but the query failed as the HBase coprocessor interface signature has been changed. Now I am planning to upgrade my cluster to CDH 5.8 (with HBase 1.2.0). Could anyone help confirm that Kylin 1.5.3 is compatible with this version of HBase ? Thanks ! CDH5.8 Packaging Information http://www.cloudera.com/documentation/enterprise/release-notes/topics/cdh_vd_cdh_package_tarball_58.html#topic_3 Fei Jia(费伽) Yum! China, IT 021-24078997 ________________________________ "This communication is confidential and may be legally privileged. If you are not the intended recipient, (i) please do not read or disclose to others, (ii) please notify the sender by reply mail, and (iii) please delete this communication from your system. Failure to follow this process may be unlawful. Thank you for your cooperation." ________________________________ "This communication is confidential and may be legally privileged. If you are not the intended recipient, (i) please do not read or disclose to others, (ii) please notify the sender by reply mail, and (iii) please delete this communication from your system. Failure to follow this process may be unlawful. Thank you for your cooperation."
