You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kylin.apache.org by "kangkaisen (JIRA)" <ji...@apache.org> on 2017/07/19 11:02:00 UTC

[jira] [Commented] (KYLIN-1926) Loosen the constraint on FK-PK data type matching

    [ https://issues.apache.org/jira/browse/KYLIN-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092932#comment-16092932 ] 

kangkaisen commented on KYLIN-1926:
-----------------------------------

I wonder what's the theoretical basis that we could loosen the constraint ?

> 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)