Github user neggert commented on the issue:
https://github.com/apache/spark/pull/15018
My thought was that there's nothing in the computation that prevents it
(unlike 0 weights, which cause NaNs). Why not err on the side of maximum
flexibility to the end user? Just because there's no use case for it now
doesn't mean someone won't find one in the future.
Just my 2 cents. I don't feel strongly about it and will defer to commiters.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
