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

Posted to issues@calcite.apache.org by "Jin Xing (Jira)" <ji...@apache.org> on 2020/04/15 12:36:00 UTC

[jira] [Updated] (CALCITE-3758) FilterTableScanRule generate wrong mapping for filter condition when underlying is BindableTableScan

     [ https://issues.apache.org/jira/browse/CALCITE-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jin Xing updated CALCITE-3758:
------------------------------
    Description: When FilterTableScanRule push filter condition into ProjectableFilterableTable, the filter condition should be adjusted to be based on the internal table of BindableTableScan.  (was: When FilterTableScanRule push filter condition into ProjectableFilterableTable, the filter condition should be adjusted to be based on the internal table of BindableTableScan.

This line[1] is rectified as *Mappings.source*

[1][https://github.com/apache/calcite/blob/571731b80a58eb095ebac7123285c375e7afff90/core/src/main/java/org/apache/calcite/rel/rules/FilterTableScanRule.java#L124])

> FilterTableScanRule generate wrong mapping for filter condition when underlying is BindableTableScan
> ----------------------------------------------------------------------------------------------------
>
>                 Key: CALCITE-3758
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3758
>             Project: Calcite
>          Issue Type: Improvement
>          Components: core
>            Reporter: Jin Xing
>            Assignee: Jin Xing
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When FilterTableScanRule push filter condition into ProjectableFilterableTable, the filter condition should be adjusted to be based on the internal table of BindableTableScan.



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