[jira] [Commented] (DRILL-5713) Doing joins on tables that share column names in a JDBC store returns incorrect results
[ https://issues.apache.org/jira/browse/DRILL-5713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654384#comment-16654384 ] Carolina Gomes commented on DRILL-5713: --- Hello, is there any ETA to when this bug will be solved? It is pretty basic and prevents joining in cases where column names are the same, no matter the plugin. > 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: +---+-+---+ > | 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 | > +---++ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-5713) Doing joins on tables that share column names in a JDBC store returns incorrect results
[ https://issues.apache.org/jira/browse/DRILL-5713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16122513#comment-16122513 ] Timothy Farkas commented on DRILL-5713: --- Discussed with Paul Rogers and Juinfeng. This will actually be difficult to do since we would have to change drill's column name references to hold the table and schema information propagate that information to the operators. We should probably fix this correctly at some point, but it is not urgent for now so I will put this ticket on the back burner. > 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 >Affects Versions: 1.11.0 > Environment: My mac running the latest drill in embedded mode. >Reporter: Timothy Farkas >Assignee: Timothy Farkas > 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: +---+-+---+ > | 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 | > +---++ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
