You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Jesus Camacho Rodriguez (JIRA)" <ji...@apache.org> on 2015/08/03 13:38:04 UTC
[jira] [Commented] (CALCITE-826) Use ProjectFactory in
RelOptUtil.pushDownJoinConditions
[ https://issues.apache.org/jira/browse/CALCITE-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651763#comment-14651763 ]
Jesus Camacho Rodriguez commented on CALCITE-826:
-------------------------------------------------
[~julianhyde], this is an issue that we were hitting in the Hive test run; as the Project operators were not created with a factory we were hitting the assertion in L394 in RelFieldTrimmer. I have created a pull request for the fix. Can I push it to master?
> Use ProjectFactory in RelOptUtil.pushDownJoinConditions
> -------------------------------------------------------
>
> Key: CALCITE-826
> URL: https://issues.apache.org/jira/browse/CALCITE-826
> Project: Calcite
> Issue Type: Bug
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
> Fix For: 1.4.0-incubating
>
>
> RelOptUtil.pushDownJoinConditions is called in FilterJoinRule; it might create Project operators, but a ProjectFactory parameter is not provided.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)