Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4844#issuecomment-76677414
I imagine there are lots of fields that could and even should be `private`.
The question is where to draw the line, since I don't think we want to hit the
whole code base in one go. What other classes in this package logically go with
the changed files? I think it would be reasonable to lock them down too as part
of this PR, unless it would make this change much larger. That seems like one
reasonable bright line to draw.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
