Github user kevincox commented on the issue:
    The thing is that if you to `take(1)` you have to evaluate the dataframe 
(at least partially) to see if there are any nulls.  It has very significant 
overhead. This version, which works inline, has near-zero overhead. 
    As for use case it is for correctness. I would rather see an error that I 
am getting nulls in a field in which I didn't expect then have my computation 
silently give the wrong answer. You can imagine that if I am counting money, or 
checking audit logs I wouldn't want to drop a row because it didn't look how I 
expected it would. 

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to