[
https://issues.apache.org/jira/browse/KYLIN-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16093134#comment-16093134
]
Shaofeng SHI commented on KYLIN-1926:
-------------------------------------
In many cases the FK and PK types are not "exact" match, but they are somehow
can be joined, such as int and long, char and varchar, etc. So it is too strict
if stops user from continue due to this.
Now this is changed to give a warning when detecting the types are different.
User can select continue or get back to double check. I think this is more
reasonable.
> Loosen the constraint on FK-PK data type matching
> -------------------------------------------------
>
> Key: KYLIN-1926
> URL: https://issues.apache.org/jira/browse/KYLIN-1926
> Project: Kylin
> Issue Type: Improvement
> Components: Metadata
> Affects Versions: all
> Reporter: Shaofeng SHI
> Assignee: Shaofeng SHI
> Priority: Minor
> Fix For: v1.5.4
>
> Attachments: 0001-KYLIN-1926-FK-PK-data-type-matching.patch
>
>
> If lookup table's PK datatype isn't equal to fact table's FK datatype, Kylin
> will report error saying "Primary key are not consistent with Foreign key".
> This constraint is too strong. Should allow user to disable this check.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
