stuhood commented on issue #21207: URL: https://github.com/apache/datafusion/issues/21207#issuecomment-5036866457
> For these cases, I think the `CASE hash` should be opt-in or easy removable (ex. we currently have a merge() implementation which merges all per-partition expressions into a range + in list). Yea, possibly. I think that this is another flavor of: > I suppose that one way to think about it though is that the CASE expression exposes strictly more information than the OR'd lists do > ... > So maybe the right answer is to expose as much information as you have, and then let the consumer decide what to do with it? It seems like it's a question of whether you need a setting to disable `CASE` expressions (which might harm unrelated consumers of the filter who _can_ consume a case expression), or whether there is a way that a consumer can "simplify an expression (by making it lossy)" at runtime. i.e.: who chooses to simplify-the-expression/discard-the-extra-information. -- 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]
