On Fri, Mar 6, 2015 at 5:36 PM, dong wang <[email protected]> wrote:
> kylin_metadata > kylin_metadata_acl > kylin_metadata_qa > kylin_metadata_qa_acl > kylin_metadata_qa_cube > kylin_metadata_qa_dict > kylin_metadata_qa_invertedindex > kylin_metadata_qa_job > kylin_metadata_qa_job_output > kylin_metadata_qa_proj > kylin_metadata_qa_table_snapshot > kylin_metadata_qa_user > kylin_metadata_user > ​Upon starting, Kylin will check if these metadata tables exists, if yes, it will reuse them, otherwise it will create them. In 0.6 versions, metadata are spread in multiple tables categoried by modules, that why you're seeing: kylin_metadata_qa_acl kylin_metadata_qa_cube kylin_metadata_qa_dict kylin_metadata_qa_invertedindex kylin_metadata_qa_job kylin_metadata_qa_job_output kylin_metadata_qa_proj kylin_metadata_qa_table_snapshot kylin_metadata_qa_user In 0.7 versions, we will only use an "all in one" table, so if you're using 0.7 versions, "kylin_metadata_qa" will replace all the above tables starting with "kylin_metadata_qa". Check out code: https://github.com/KylinOLAP/Kylin/blob/a3b4bccd90fe0852a93dd91f68cb37f08f8719f7/common/src/main/java/org/apache/kylin/common/persistence/HBaseResourceStore.java#L90
