hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Igor Kryvenko (JIRA)" <>
Subject [jira] [Commented] (HIVE-18725) Improve error handling for subqueries if there is wrong column reference
Date Wed, 22 Aug 2018 06:06:00 GMT


Igor Kryvenko commented on HIVE-18725:

[~vgarg] Hi Vineet. I've fully reworked my patch. Now, I just throw the {{CalciteSubquerySemanticException}}
from subquery code. 
Also, I've built hive from source code, and run several queries with invalid columns in the
subqueries, and I've got the correct errors.

Could, you please take another look?

Thanks, Igor.

> Improve error handling for subqueries if there is wrong column reference
> ------------------------------------------------------------------------
>                 Key: HIVE-18725
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Planning
>            Reporter: Vineet Garg
>            Assignee: Igor Kryvenko
>            Priority: Major
>         Attachments: HIVE-18725.01.patch, HIVE-18725.02.patch, HIVE-18725.03.patch, HIVE-18725.04.patch,
HIVE-18725.05.patch, HIVE-18725.06.patch, HIVE-18725.07.patch, HIVE-18725.08.patch, HIVE-18725.09.patch,
> If there is a column reference within subquery which doesn't exist Hive throws misleading
error message.
> e.g. 
> {code:sql}
> select * from table1 where table1.col1 IN (select col2 from table2 where table2.col1=table1.non_existing_column)
and table1.col1 IN (select 4);
> {code}
> The above query, assuming table1 doesn't have non_existing_column, will throw following
misleading error:
> {noformat}
> FAILED: SemanticException Line 0:-1 Unsupported SubQuery Expression 'col1': Only 1 SubQuery
expression is supported.
> {noformat}

This message was sent by Atlassian JIRA

View raw message