[GitHub] [arrow-datafusion] andygrove opened a new issue, #2600: filter_push_down tests should not rely on TableProvider and ExecutionPlan

[GitBox <gi...@apache.org>]

andygrove opened a new issue, #2600:
URL: https://github.com/apache/arrow-datafusion/issues/2600

   **Is your feature request related to a problem or challenge? Please describe what you are trying to do.**
   I would like to move the logical optimization rules to their own crate (https://github.com/apache/arrow-datafusion/issues/2599) and this 
   means that they should not depend on the physical plan.
   
   `filter_push_down` tests currently rely on `TableProvider` and `ExecutionPlan`
   
   **Describe the solution you'd like**
   Remove the dependency and rewrite the tests to just use the logical plan
   
   **Describe alternatives you've considered**
   None
   
   **Additional context**
   None
   


-- 
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: github-unsubscribe@arrow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [arrow-datafusion] alamb closed issue #2600: filter_push_down tests should not rely on TableProvider and ExecutionPlan

[GitBox <gi...@apache.org>]

alamb closed issue #2600: filter_push_down tests should not rely on TableProvider and ExecutionPlan
URL: https://github.com/apache/arrow-datafusion/issues/2600


-- 
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: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org