Github user mgaido91 commented on the issue:
https://github.com/apache/spark/pull/21882
@pwoody I am not sure I 100% agree on your last sentence. I agree that we
should correct null bounds, but letting the users facing bugs returning wrong
results meanwhile we find all the possible cases we have not thought of is not
the right way to go I think. Moreover, if a datatype is not orderable, we
cannot even fix the lack of an upper and lower bound...
I think the approach proposed here is safer and I like it. It would be
great (but I am not sure it is feasible) if we could emit a WARN message in
case a null is found (in testing we can throw an exception using
`AssertNotNull`), in order to let users know that they are hitting a case which
should not happen, so that they can report us.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
