Github user MLnick commented on the issue:

    https://github.com/apache/spark/pull/15149
  
    Hmm, yes that would be an inconsistent scenario cos `thresholds` would be 
used in that case rather than `threshold`. And `threshold` could have been set 
to `0` => `thresholds = [1, 0]` (or set to `1` => `[0, 1]`). Even though it's 
most likely users would use binary classification with binomial, this is 
definitely a corner case.
    
    Either way it could blow up the calculation. So we could just allow at most 
one threshold to be `0`. And in this case always predict that class.


---
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

Reply via email to