[
https://issues.apache.org/jira/browse/KYLIN-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926401#comment-16926401
]
ASF GitHub Bot commented on KYLIN-4159:
---------------------------------------
nichunen commented on pull request #835: KYLIN-4159 The first step of job will
fail and throw "Column \'xx\' i…
URL: https://github.com/apache/kylin/pull/835
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> The first step of build cube job will fail and throw "Column 'xx' in where
> clause is ambiguous" in jdbc datasource.
> -------------------------------------------------------------------------------------------------------------------
>
> Key: KYLIN-4159
> URL: https://issues.apache.org/jira/browse/KYLIN-4159
> Project: Kylin
> Issue Type: Bug
> Reporter: luguosheng
> Assignee: luguosheng
> Priority: Major
>
> Reappear:
> In the model of kylin, If we have a column used as a partition column in the
> fact table, and there is a column in lookup table has the same name. It can
> be reappeared。
> RootCause:
> In jdbc datasource , we use Sqoop option "--boundary-query sql" to split
> data, the sql like "select max(partition_column), min(partition_column) from
> flat_table where flat_table.partition_column> 20120101 and
> flat_table.partition.column < 20190101" and there is more than one column
> which have the same name of the "partition_column" in the flat_table. the sql
> driver can not distinguish the table that partition_column belong to。
> How to resolve:
> Alter the sql like: "select max(t.partition_column),min(t.partition_column)
> from flat_table where flat_table.partition_column> 20120101 and
> flat_table.partition.column < 20190101"
>
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
