Hi, Iñigo Martínez. If you meet too many problems with HBase, you can try to use MySQL instead. Hope this can help you. http://kylin.apache.org/docs/tutorial/mysql_metastore.html. In HBase, there is one metadata_table. In MySQL, there are two metadata_tables. So I think you can not migrate metadata from HBase to MySQL directly.
发送自 Windows 10 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>应用 ________________________________ 发件人: Iñigo Martínez <[email protected]> 发送时间: Thursday, March 14, 2019 10:40:27 PM 收件人: [email protected] 主题: Upgrade from 2.4.1 to 2.6.1 Now that 2.6.1 is launched, we are planning an upgrade (with a transition period and an extensive test plan) from 2.4.1. I have a few questions for developers and / or system administrators. - Do you recommend use mysql as kylin metadata storage? Until now, most of our problems are related with hbase since we rebuild cubes very frequently and kylin_metadata table grows a lot. Do you notice performance loss or gain? Is it stable enough? - If using mysql as metadata backend, can we export / import metadata in order to migrate from hbase to mysql without having rebuild existing cubes? Thanks in advance.
