Github user His-name-is-Joof commented on the pull request:
https://github.com/apache/spark/pull/6319#issuecomment-105292808
In my opinion, it seems like a poor fix to the issue of composing Batches
in different instances and there is likely a much better way to refactor
the class to get the desired behavior (although I don't personally know how
yet). It was labeled as starter and making the classes outer was the
proposed fix.
On May 24, 2015 11:48 PM, "Cheng Hao" <[email protected]> wrote:
> Any background why we should expose the Batch? Per my understanding, we'd
> better keep the minimizing the class visibility as much as possible in
> design.
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/spark/pull/6319#issuecomment-105133466>.
>
---
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]
