[
https://issues.apache.org/jira/browse/DRILL-5713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volodymyr Vysotskyi updated DRILL-5713:
---------------------------------------
Description:
If there are two tables in Postgres that share column names, incorrect results
are returned when a join is done between the two tables.
For example if we have two tables: categories and categories2 with the
following contents:
{noformat}
+----------------+--------------------++---------------
|categoryguid|categoryparentguid|categoryname|
+----------------+--------------------++---------------
|id1|null|restaurants|
|null|id1|food&Dining|
|id2|null|Coffee Shops|
|null|id2|food&Dining|
+----------------+--------------------++---------------
{noformat}
Then the following join query returns incorrectly names columns and incorrect
null values:
{code:sql}
select cat.categoryname, cat2.categoryname from postgres.public.categories cat
join postgres.public.categories2 cat2 on (cat.categoryguid = cat2.categoryguid)
where cat.categoryguid IS NOT NULL;
{code}
{noformat}
+----------------+---------------+
|categoryname|categoryname0|
+----------------+---------------+
|restaurants|null|
|Coffee Shops|null|
+----------------+---------------+
{noformat}
was:
If there are two tables in Postgres that share column names, incorrect results
are returned when a join is done between the two tables.
For example if we have two tables: categories and categories2 with the
following contents:
+---------------+---------------------+---------------+
| categoryguid | categoryparentguid | categoryname |
+---------------+---------------------+---------------+
| id1 | null | restaurants |
| null | id1 | food&Dining |
| id2 | null | Coffee Shops |
| null | id2 | food&Dining |
+---------------+---------------------+---------------+
Then the following join query returns incorrectly names columns and incorrect
null values:
select cat.categoryname, cat2.categoryname from
postgres.public.categories cat join postgres.public.categories2 cat2 on
(cat.categoryguid = cat2.categoryguid) where cat.categoryguid IS NOT NULL;
+---------------+----------------+
| categoryname | categoryname0 |
+---------------+----------------+
| restaurants | null |
| Coffee Shops | null |
+---------------+----------------+
> Doing joins on tables that share column names in a JDBC store returns
> incorrect results
> ---------------------------------------------------------------------------------------
>
> Key: DRILL-5713
> URL: https://issues.apache.org/jira/browse/DRILL-5713
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Relational Operators, Storage - JDBC
> Affects Versions: 1.11.0
> Environment: My mac running the latest drill in embedded mode.
> Reporter: Timothy Farkas
> Assignee: Timothy Farkas
> Priority: Major
> Labels: newbie
>
> If there are two tables in Postgres that share column names, incorrect
> results are returned when a join is done between the two tables.
> For example if we have two tables: categories and categories2 with the
> following contents:
> {noformat}
> +----------------+--------------------++---------------
> |categoryguid|categoryparentguid|categoryname|
> +----------------+--------------------++---------------
> |id1|null|restaurants|
> |null|id1|food&Dining|
> |id2|null|Coffee Shops|
> |null|id2|food&Dining|
> +----------------+--------------------++---------------
> {noformat}
> Then the following join query returns incorrectly names columns and incorrect
> null values:
> {code:sql}
> select cat.categoryname, cat2.categoryname from postgres.public.categories
> cat join postgres.public.categories2 cat2 on (cat.categoryguid =
> cat2.categoryguid) where cat.categoryguid IS NOT NULL;
> {code}
> {noformat}
> +----------------+---------------+
> |categoryname|categoryname0|
> +----------------+---------------+
> |restaurants|null|
> |Coffee Shops|null|
> +----------------+---------------+
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
