You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by "westonpace (via GitHub)" <gi...@apache.org> on 2023/04/11 17:00:39 UTC

[GitHub] [arrow] westonpace commented on issue #34982: Relax pyarrow.compute.is_in type requirement

westonpace commented on issue #34982:
URL: https://github.com/apache/arrow/issues/34982#issuecomment-1503779935

   It's a good idea but there isn't a good spot for this kind of optimization today so it'll be challenging to add.  It might be possible to do this with implicit casting.  Type coercion (implicit casting) happens today when expressions move from unbound (not tied to any input schema) to bound (tied to a specific input schema).
   
   This type coercion is enabled per-function so maybe SetLookupFunction could have a custom DispatchBest implementation that first attempts to dispatch exact and, if that fails, changes to a custom "always return false" function :shrug: 
   
   Either way, we don't have much precedent for this kind of thing and I think one could argue that this should be solved higher up than Arrow compute in some kind of expression rewrite pass (this doesn't exist today either).


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