tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hyunsik Choi (JIRA)" <j...@apache.org>
Subject [jira] [Created] (TAJO-363) Columns in subquery schema cannot be resolved
Date Tue, 03 Dec 2013 04:51:38 GMT
Hyunsik Choi created TAJO-363:
---------------------------------

             Summary: Columns in subquery schema cannot be resolved
                 Key: TAJO-363
                 URL: https://issues.apache.org/jira/browse/TAJO-363
             Project: Tajo
          Issue Type: Bug
          Components: parser, planner/optimizer
            Reporter: Hyunsik Choi
            Priority: Critical
             Fix For: 0.8-incubating


See the below SQL statement. This statement contains a subquery with schema binding. Currently,
LogicalPlanner cannot recognize subquery schema. So,  the below statement causes "no such
a column name  exception".

{code}
select 
  c_count, 
  count(*) as custdist 
from 
( 
  select 
    c_custkey, 
    count(o_orderkey) 
  from 
    customer left outer join 
    orders 
      on c_custkey = o_custkey and 
      o_comment not like '%special%requests%' 
  group by 
    c_custkey 

) as c_orders (c_custkey, c_count) 

group by 
	c_count 
order by 
	custdist desc, c_count desc;


ERROR: no such a column name c_count
{code}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message