andygrove commented on pull request #8785: URL: https://github.com/apache/arrow/pull/8785#issuecomment-734910372
With this syntax, the WHERE clause can contain both JOIN conditions and regular filter conditions. For example: ```sql FROM customer, orders, lineitem WHERE c_mktsegment = 'BUILDING' AND c_custkey = o_custkey AND l_orderkey = o_orderkey AND o_orderdate < date '1995-03-15' AND l_shipdate > date '1995-03-15' ``` I think there are two options for addressing this. 1. Have the SQL planner remove the join expressions from the filter expression 2. Modify the filter push down logic to prevent filters being pushed through joins when they reference both join inputs I'm not sure which approach is best. ---------------------------------------------------------------- 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