You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "pengzhiwei (JIRA)" <ji...@apache.org> on 2018/06/26 11:09:00 UTC

[jira] [Created] (CALCITE-2382) Column not found when subquery join lateral table function

pengzhiwei created CALCITE-2382:
-----------------------------------

             Summary: Column not found when subquery join lateral table function
                 Key: CALCITE-2382
                 URL: https://issues.apache.org/jira/browse/CALCITE-2382
             Project: Calcite
          Issue Type: Bug
          Components: core
    Affects Versions: 1.16.0
            Reporter: pengzhiwei
            Assignee: Julian Hyde


When use subquery join lateral table function as followed:

 
{code:java}
 select * from ( select 5 as f0 from s.t ) a,lateral table(s.GenerateStrings(f0)) as t(n, c)  where char_length(c) > 3
{code}
'SqlValidatorException: Column 'F0' not found in any table'  has thrown out.

I find the reason is that  SqlValidatorImpl add the Identifier 's.t' namespace to the children of tableScope,but not the subquey's namespace,just as the code show bellow in  SqlValidatorImpl#registerFrom:

 
{code:java}
case IDENTIFIER:
  ...........
  if (tableScope == null) {
  tableScope = new TableScope(parentScope, node);
  }
 tableScope.addChild(newNs, alias, forceNullable);{code}
 

 

I think the namespace of  JoinScope's left child should be right for the child of tableScope which was referenced by the table function,just as the code show bellow in  SqlValidatorImpl#registerFrom:
{code:java}
case COLLECTION_TABLE:
  ....
  TableScope tableScope = null;

  if(parentScope instanceof JoinScope) {

  tableScope = new TableScope(new EmptyScope(this),operand);
  JoinScope scope = (JoinScope) parentScope;

  SqlValidatorNamespace leftNs = scope.getChildren().get(0);

  tableScope.addChild(leftNs,scope.children.get(0).name,forceNullable);
}
....{code}
After this modification,the case upon runs well.

Is there any problem for this modification? Any suggestions is welcomed.Thanks a lot.

 

 

 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)