[jira] [Comment Edited] (CALCITE-55) Don't create sets that are just a column-permutation of an existing set

["Julian Hyde (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CALCITE-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14035032#comment-14035032 ] 

Julian Hyde edited comment on CALCITE-55 at 3/9/21, 10:15 PM:
--------------------------------------------------------------

[Date: Tue Jan 14 02:04:25 CET 2014, Author: [julianhyde|https://github.com/julianhyde]]

Similar to CALCITE-62.


was (Author: github-import):
[Date: Tue Jan 14 02:04:25 CET 2014, Author: [julianhyde|https://github.com/julianhyde]]

Similar to ([#62|https://github.com/JulianHyde/optiq/issues/62] | [FLINK-62|https://issues.apache.org/jira/browse/OPTIQ-62]).

> Don't create sets that are just a column-permutation of an existing set
> -----------------------------------------------------------------------
>
>                 Key: CALCITE-55
>                 URL: https://issues.apache.org/jira/browse/CALCITE-55
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: GitHub Import
>            Priority: Major
>              Labels: github-import
>
> Don't create sets that are just a column-permutation of an existing set. For example, if setX has columns [c0, c1, c2, c3] and the the expression 'Project(setX, c2, c3, c1, c0)' is registered, don't create a new setY.
> This change would reduce the number of almost-identical sets and reduce the number of rules that need to fire.
> I'm not sure whether it's possible to put 'Project(setX, c0, c1)', which has a subset of columns, in setX.
> ---------------- Imported from GitHub ----------------
> Url: https://github.com/julianhyde/optiq/issues/55
> Created by: [julianhyde|https://github.com/julianhyde]
> Labels: 
> Created at: Fri Sep 27 01:14:50 CEST 2013
> State: open



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