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

Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2022/10/20 18:31:30 UTC

[GitHub] [arrow-datafusion] alamb commented on issue #3898: A framework for expression boundary analysis (and statistics)

alamb commented on issue #3898:
URL: https://github.com/apache/arrow-datafusion/issues/3898#issuecomment-1285974788

   I love this idea @isidentical  -- thank you for filing it -- I am still not quite sure about how well keeping `column_boundaries` would work in practice, but I think I would just have to see how it works in practice to find out. 
   
   I also wonder what "apply"ing boundaries to a `PhysicalExpr` means -- does it mean the output of the PhysicalExpr might change when run against some data? Does it mean the `PhysicalExpr` might change? Or is it solely to update the `AnalysisContext`?


-- 
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