You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Danny Chen (Jira)" <ji...@apache.org> on 2020/02/20 05:34:00 UTC

[jira] [Updated] (CALCITE-3369) In LatticeSuggester, recommend lattices based on UNION queries

     [ https://issues.apache.org/jira/browse/CALCITE-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Danny Chen updated CALCITE-3369:
--------------------------------
    Fix Version/s:     (was: 1.22.0)

> In LatticeSuggester, recommend lattices based on UNION queries
> --------------------------------------------------------------
>
>                 Key: CALCITE-3369
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3369
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>            Priority: Major
>
> In LatticeSuggester, recommend lattices based on UNION, EXCEPT and INTERSECT queries. Currently such queries are ignored.
> Given the query
> {code:java}
> select * from t1 join t2
> union
> select * from t2 join t3;{code}
> suggester should generate the same lattice(s) as if it had been given two separate queries
> {code:java}
> select * from t1 join t2;
> select * from t2 join t3; {code}
> Which may be a single lattice t1 - t2 - t3, or might be two lattices t1 - t2, t2 - t3.
> Same for EXCEPT (MINUS), INTERSECT, UNION ALL, etc.
> If the set-op is internal, I'm not sure what to do, e.g.
> {code:java}
> select *
> from sales
> join (select * from good_product
>       union
>       select * from bad_product) using (product_id){code}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)