Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/4844#issuecomment-76860788
yeah, in many cases, the class is exposed as `private[spark]` unnecessarily
with/without proper restrictions for members
I scan the code base, found that this is not an intentional design , as in
some classes like
https://github.com/CodingCat/spark/blob/SPARK-4011/core/src/main/scala/org/apache/spark/deploy/history/HistoryServerArguments.scala#L26
the class is restricted in its local package, which I thought to be the
right choice
so I followed this idea and made the changes
---
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]
