You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2015/01/13 21:19:35 UTC

[jira] [Created] (CALCITE-557) Remove AbstractConverter

Julian Hyde created CALCITE-557:
-----------------------------------

             Summary: Remove AbstractConverter
                 Key: CALCITE-557
                 URL: https://issues.apache.org/jira/browse/CALCITE-557
             Project: Calcite
          Issue Type: Bug
            Reporter: Julian Hyde
            Assignee: Julian Hyde


Currently each subset contains an AbstractConverter to each subset in the same set. If there are a lot of active traits, there are many, many AbstractConverters that do not add anything to the planning.

This task would remove those AbstractConverters. In fact AbstractConverter would never be created.

Also, make costing of joins more deterministic when both inputs have the same number of rows. Currently we use the RelNode.id of the inputs, but this is unstable if we change what rules are activated. So, we should order the inputs based on the number of columns first, and on id only if that fails.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)