houqp commented on a change in pull request #9309: URL: https://github.com/apache/arrow/pull/9309#discussion_r566379027
########## File path: rust/datafusion/src/optimizer/boolean_comparison.rs ########## @@ -0,0 +1,270 @@ +// Licensed to the Apache Software Foundation (ASF) under one +// or more contributor license agreements. See the NOTICE file +// distributed with this work for additional information +// regarding copyright ownership. The ASF licenses this file +// to you under the Apache License, Version 2.0 (the +// "License"); you may not use this file except in compliance +// with the License. You may obtain a copy of the License at +// +// http://www.apache.org/licenses/LICENSE-2.0 +// +// Unless required by applicable law or agreed to in writing, +// software distributed under the License is distributed on an +// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +// KIND, either express or implied. See the License for the +// specific language governing permissions and limitations +// under the License. + +//! Boolean comparision rule rewrites redudant comparison expression involing boolean literal into +//! unary expression. + +use std::sync::Arc; + +use crate::error::Result; +use crate::logical_plan::{Expr, LogicalPlan, Operator}; +use crate::optimizer::optimizer::OptimizerRule; +use crate::optimizer::utils; +use crate::scalar::ScalarValue; + +/// Optimizer that simplifies comparison expressions involving boolean literals. +/// +/// Recursively go through all expressionss and simplify the following cases: +/// * `expr = ture` to `expr` +/// * `expr = false` to `!expr` +pub struct BooleanComparison {} + +impl BooleanComparison { Review comment: yeah, totally, agree, i was really tempting to introduce an optimization framework while writing those tree traversal boilerplate code, but decided it's probably better be done as a separate refactoring so we can get a better feeling of how the new framework can affect all the existing rules. the way we are currently managing optimization rules is definitely too raw ;) I will take a look at the Expression Visitor pattern as well since that's something already exists in the code base. ########## File path: rust/datafusion/src/optimizer/boolean_comparison.rs ########## @@ -0,0 +1,270 @@ +// Licensed to the Apache Software Foundation (ASF) under one +// or more contributor license agreements. See the NOTICE file +// distributed with this work for additional information +// regarding copyright ownership. The ASF licenses this file +// to you under the Apache License, Version 2.0 (the +// "License"); you may not use this file except in compliance +// with the License. You may obtain a copy of the License at +// +// http://www.apache.org/licenses/LICENSE-2.0 +// +// Unless required by applicable law or agreed to in writing, +// software distributed under the License is distributed on an +// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +// KIND, either express or implied. See the License for the +// specific language governing permissions and limitations +// under the License. + +//! Boolean comparision rule rewrites redudant comparison expression involing boolean literal into +//! unary expression. + +use std::sync::Arc; + +use crate::error::Result; +use crate::logical_plan::{Expr, LogicalPlan, Operator}; +use crate::optimizer::optimizer::OptimizerRule; +use crate::optimizer::utils; +use crate::scalar::ScalarValue; + +/// Optimizer that simplifies comparison expressions involving boolean literals. +/// +/// Recursively go through all expressionss and simplify the following cases: +/// * `expr = ture` to `expr` +/// * `expr = false` to `!expr` +pub struct BooleanComparison {} + +impl BooleanComparison { Review comment: yeah, totally, agree with both of you, i was really tempting to introduce an optimization framework while writing those tree traversal boilerplate code, but decided it's probably better be done as a separate refactoring so we can get a better feeling of how the new framework can affect all the existing rules. the way we are currently managing optimization rules is definitely too raw ;) I will take a look at the Expression Visitor pattern as well since that's something already exists in the code base. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
