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/28 21:44:37 UTC
[jira] [Updated] (CALCITE-575) Variant of ProjectRemoveRule that
considers a project trivial only if field names are identical
[ https://issues.apache.org/jira/browse/CALCITE-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Hyde updated CALCITE-575:
--------------------------------
Description:
CALCITE-92 seems to have changed behavior of ProjectRemoveRule to discard field names while considering if a project is trivial. Unfortunately they way Hive is integrated with Calcite we would need to preserve names.
This issue would go away once Calcite Operators get converted to Hive Operators as opposed to Hive AST.
was:
Calcite-92 seems to have changed behavior of ProjectRemoveRule to discard field names while considering if a project is trivial. Unfortunately they way Hive is integrated with Calcite we would need to preserve names.
This issue would go away once Calcite Operators get converted to Hive Operators as opposed to Hive AST.
> Variant of ProjectRemoveRule that considers a project trivial only if field names are identical
> -----------------------------------------------------------------------------------------------
>
> Key: CALCITE-575
> URL: https://issues.apache.org/jira/browse/CALCITE-575
> Project: Calcite
> Issue Type: Bug
> Reporter: Laljo John Pullokkaran
> Assignee: Laljo John Pullokkaran
> Attachments: CALCITE-575.patch
>
>
> CALCITE-92 seems to have changed behavior of ProjectRemoveRule to discard field names while considering if a project is trivial. Unfortunately they way Hive is integrated with Calcite we would need to preserve names.
> This issue would go away once Calcite Operators get converted to Hive Operators as opposed to Hive AST.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)