Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/1327#issuecomment-48571146
The reason to initialize size upfront and keep it immutable is to enforce
constraints on the writer since it is lazily initialized.
On Jul 10, 2014 10:29 AM, "Saisai Shao" <notificati...@github.com> wrote:
> IMHO, if we leave reuse of this object aside, I don't think this change
> will bring specific effect to the current code path. If we really want to
> defend the reuse of this object, there's no conflict with adding closed
> flag. Also this change align with other field which are all initialized in
> the initialize(), not constructor....
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/spark/pull/1327#issuecomment-48565390>.
>
---
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.
---
