[KYLIN-4159] The first step of build cube job will fail and throw "Column 'xx' in where clause is ambiguous" in jdbc datasource.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: v3.0.0-beta, v2.6.4
• Assignee: luguosheng
• Reporter: luguosheng
• Created: 05/Sep/19 16:26
• Updated: 13/Oct/19 00:37
• Resolved: 18/Sep/19 03:12

Description

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"

 

 

Issue Links

• links to: GitHub Pull Request #835