Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14555
That's a good point, it's public now. I think I agree with you then, it's
fairly important to retain the validation there. It would also be inconsistent
to move it back, yes, because I see the other factory methods don't do the same
validation.
I suppose that if it were a big issue we could find a way to expose a
private alternative constructor that skips validation where internal code knows
the inputs are valid.
---
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
