You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Ruixuan Zhang (Jira)" <ji...@apache.org> on 2023/02/16 03:02:00 UTC

[jira] [Updated] (KYLIN-5445) Epoch tables of metadata are created without primary key, which results in failure creating table under specific versions of database

     [ https://issues.apache.org/jira/browse/KYLIN-5445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ruixuan Zhang updated KYLIN-5445:
---------------------------------
    Summary: Epoch tables of metadata are created without primary key, which results in failure creating table under specific versions of database  (was: Epoch tables of metadata sometimes are created without primary key through mysql, results in failure creating table using certain versions of database)

> Epoch tables of metadata are created without primary key, which results in failure creating table under specific versions of database
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KYLIN-5445
>                 URL: https://issues.apache.org/jira/browse/KYLIN-5445
>             Project: Kylin
>          Issue Type: Bug
>          Components: Metadata
>    Affects Versions: 5.0-alpha
>            Reporter: Ruixuan Zhang
>            Priority: Major
>             Fix For: 5.0-alpha
>
>
> When KYLIN using jdbc to create epoch table, sometimes creating table will results in failure under certain versions of database due to that table not specifying the primary key.
> Therefore, the field target_epoch can be used as primary key, and its previous constraint of being unique can be removed. For the environment that the table has already exist, KYLIN will firstly check if the primary key exists, if so, then target_epoch will be added as primary key.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)