Kenneth Knowles commented on BEAM-8817:

I spent some time on this. I wanted them to actually share the main planner. 
But actually each dialect has some of their own custom rules. So it is more of 
a fancy project to separate the planners. Calcite also really wants there to be 
just one planner so sharing logic can be hard. Going to close this as won't fix.

> Beam SQL dialects should share table registration and name resolution logic
> ---------------------------------------------------------------------------
>                 Key: BEAM-8817
>                 URL: https://issues.apache.org/jira/browse/BEAM-8817
>             Project: Beam
>          Issue Type: Improvement
>          Components: dsl-sql, dsl-sql-zetasql
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>            Priority: Major
> Currently the ZetaSQL and Calcite SQL code paths each have their own version 
> of "scrape the table names from the query" and "let the table providers know 
> that we will be asking for these names". There should be a common abstraction 
> for this.

This message was sent by Atlassian Jira

Reply via email to