cetra3 commented on PR #21743: URL: https://github.com/apache/datafusion/pull/21743#issuecomment-4402298063
> > I know this is already merged, but this one PR has broken a lot of our code internally, due to the structural changes around this. (i.e, #22053) > > Is there any chance we can make this an optimization pass that can switch off this behaviour, rather than something that is always baked in. > > Could you elaborate on what broke (beyond the linked issue) and which behaviour you're referring to here? The support of `ANY <> array()` itself, or the translation of it to case statements in order to follow postgres semantics? I've investigated this more. The shape to the `LogicalPlan` has actually broken *a lot* of things. Stats min/max pruning, page-index pruning, and bloom filter pruning are all effectively disabled for any query using `ANY` I've raised an issue about it: https://github.com/apache/datafusion/issues/22073 -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
