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.
