adriangb commented on code in PR #12978:
URL: https://github.com/apache/datafusion/pull/12978#discussion_r1819101909
##########
datafusion/core/src/physical_optimizer/pruning.rs:
##########
@@ -3577,7 +3585,11 @@ mod tests {
// s1 ["A", NULL] ==> unknown (must keep)
// s1 ["", "A"] ==> some rows could pass (must keep)
// s1 ["", ""] ==> no rows can pass (not keep)
- let expected_ret = &[true, true, false, false, true, true, true,
false];
+ // s1 ["AB", "A\u{10ffff}"] ==> no rows can pass (not keep)
Review Comment:
I take it you are saying each one of these should be their own test right? I
agree that would make it a lot clear. It'd be more boilerplate code as well but
IMO it'd be worth it. I was just following the pattern other tests use, and
this started as a couple test cases and has grown considerably...
--
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]
