[
https://issues.apache.org/jira/browse/CALCITE-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14288085#comment-14288085
]
Julian Hyde commented on CALCITE-445:
-------------------------------------
As part of my fix for CALCITE-558, I am changing Calcite to not push any
filters or projects if any filters are rejected. This is safe (never produces
the wrong results) but not very efficient.
As part of this this issue we should remedy this. I think the solution may be
to have the interpreter apply some existing rules (e.g.
FilterProjectTransposeRule) in the "rewrite" phase. Maybe we can obsolete the
rewrite method altogether.
> Pull up filters rejected by a ProjectableFilterableTable
> ---------------------------------------------------------
>
> Key: CALCITE-445
> URL: https://issues.apache.org/jira/browse/CALCITE-445
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
>
> Suppose that {{t (i, j, k)}} is a table that implements
> ProjectableFilterableTable, we execute the query {{select k from t where j =
> 1}}, and {{t}} refuses to evaluate the filter {{j = 1}}.
> We should still push the project to the table. But we need to project the
> extra column, {{j}} needed by the filter, and transform it, because it now
> occurs after the project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
