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

Shaofeng SHI reassigned KYLIN-1926:
-----------------------------------

         Assignee:     (was: Shaofeng SHI)
    Fix Version/s:     (was: v1.5.4)
       Issue Type: Bug  (was: Improvement)

Kaisen, has this issue been fixed? I think you have identified the root cause, 
do you have a proposal for the fix? Thanks.

> 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: Bug
>          Components: Metadata
>    Affects Versions: all
>            Reporter: Shaofeng SHI
>            Priority: Minor
>              Labels: scope
>         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)

Reply via email to