[
https://issues.apache.org/jira/browse/KYLIN-5493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709179#comment-17709179
]
longfeiJiang edited comment on KYLIN-5493 at 4/6/23 3:54 AM:
-------------------------------------------------------------
Dev Design
When using jdbc to create an epoch table, use epoch_target as the primary key,
and the previous unique constraint is not needed
For the environment where the table has been built, first determine whether the
primary key exists, if not, add epoch_target as the primary key to maintain
consistency
The upgraded environment, the old unique is not deleted here
Evidence
new env
!image-2023-04-06-11-54-47-463.png!
upgraded env
!image-2023-04-06-11-54-33-705.png!
was (Author: JIRAUSER298472):
Dev Design
When using jdbc to create an epoch table, use epoch_target as the primary key,
and the previous unique constraint is not needed
For the environment where the table has been built, first determine whether the
primary key exists, if not, add epoch_target as the primary key to maintain
consistency
The upgraded environment, the old unique is not deleted here
Evidence
new env
upgraded env
> When creating the epoch table, add the primary key
> --------------------------------------------------
>
> Key: KYLIN-5493
> URL: https://issues.apache.org/jira/browse/KYLIN-5493
> Project: Kylin
> Issue Type: Improvement
> Reporter: longfeiJiang
> Assignee: longfeiJiang
> Priority: Major
> Attachments: image-2023-04-06-11-54-33-705.png,
> image-2023-04-06-11-54-47-463.png
>
>
> When kylin install in new env, creating the epoch table, add the primary key:
> epoch_target
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
