jackwener commented on issue #5949: URL: https://github.com/apache/arrow-datafusion/issues/5949#issuecomment-1502967580
It indeed is covered by `skip failed rule` ``` | initial_logical_plan | Filter: t.a > Int32(1) | | | Projection: t.a - t.b | | | TableScan: t | | logical_plan after simplify_expressions | SAME TEXT AS ABOVE | | logical_plan after replace_distinct_aggregate | SAME TEXT AS ABOVE | | logical_plan after decorrelate_where_exists | SAME TEXT AS ABOVE | | logical_plan after decorrelate_where_in | SAME TEXT AS ABOVE | | logical_plan after scalar_subquery_to_join | SAME TEXT AS ABOVE | | logical_plan after extract_equijoin_predicate | SAME TEXT AS ABOVE | | logical_plan after simplify_expressions | SAME TEXT AS ABOVE | | logical_plan after merge_projection | SAME TEXT AS ABOVE | | logical_plan after rewrite_disjunctive_predicate | SAME TEXT AS ABOVE | | logical_plan after eliminate_duplicated_expr | SAME TEXT AS ABOVE | | logical_plan after eliminate_filter | SAME TEXT AS ABOVE | | logical_plan after eliminate_cross_join | SAME TEXT AS ABOVE | | logical_plan after eliminate_limit | SAME TEXT AS ABOVE | | logical_plan after propagate_empty_relation | SAME TEXT AS ABOVE | | logical_plan after filter_null_join_keys | SAME TEXT AS ABOVE | | logical_plan after eliminate_outer_join | SAME TEXT AS ABOVE | | logical_plan after push_down_limit | SAME TEXT AS ABOVE | | logical_plan after push_down_filter | Projection: t.a - t.b | | | Filter: t.a > Int32(1) | | | TableScan: t ``` After I investigate it, I find the cause of this problem. This plan is wrong, but because of we don't have analyzer, so it was cover by `push_down_filter`. After `push_down_filter`, the wrong plan will be right plan. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
