[
https://issues.apache.org/jira/browse/KYLIN-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17928036#comment-17928036
]
Guoliang Sun commented on KYLIN-6001:
-------------------------------------
h3. Dev Design
After reviewing the code, it has been confirmed that upgrading the metadata
does not require modifying the table prefix, meaning the working directory will
not change, and there is no need to rebuild the models.
In Kylin5, the table structures/content of `job_info`, `job_lock`, and
`audit_log` have changed. Considering the limited significance of migration, it
is better to use new tables with updated names instead.
The new table names will be `job_info_v2`, `job_lock_v2`, and `audit_log_v2`.
> [Metadata] Kylin4 metadata cannot be directly upgraded to Kylin5. After
> customers migrate the metadata, they still need to rebuild models and other
> components.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: KYLIN-6001
> URL: https://issues.apache.org/jira/browse/KYLIN-6001
> Project: Kylin
> Issue Type: Bug
> Affects Versions: 5.0.0
> Reporter: Guoliang Sun
> Priority: Major
>
> Current method for upgrading from Kylin4 to Kylin5:
> Back up the Kylin4 metadata, migrate it to Kylin5 using the data migration
> script, and then restore the migrated data.
> Issue:
> After restoring the Kylin5 data, the models need to be rebuilt before they
> can be used.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
