Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14524
I probably need some oversight here since I'm not familiar with pyspark in
this regard, but it looks like PythonMLLibAPI treated seeds a little
differently in a few cases which meant they couldn't be null/None. That seemed
like something fix, even if not changing behavior. Yeah right now I think you
couldn't for example specify "no seed" to a few Pyspark API methods but you can
for others. Specifying None would result in 0 or something as a seed.
---
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
