[
https://issues.apache.org/jira/browse/KYLIN-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16093171#comment-16093171
]
kangkaisen commented on KYLIN-1926:
-----------------------------------
Thanks Shaofeng, I see.
Today I debugged a SQL, the inconsistent data type for FK and PK resulted in
Calcite got wrong "EXECUTION PLAN BEFORE REWRITE". Currently, I am not sure
the bug is belong to Calcite or Kylin. I will debug this issue continually.
PS, the data type for FK and PK is int and tinyint.
> 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)
