Github user carrino commented on the pull request:
https://github.com/apache/spark/pull/6293#issuecomment-105651198
Another option is to just force autoclose to be on. I think these fixes are
important enough. I'm seeing about 13% perf hit from doing reflection
creating these Kryo Serializers, so rolling this back is kinda the opposite
of what I was hoping for.
On May 26, 2015 10:29 AM, "Josh Rosen" <[email protected]> wrote:
> I discovered that this didn't entirely fix the problem, since there are
> some corner-cases where we attempt to construct multiple open
OutputStreams
> from the same serializer instance. I've opened #6415
> <https://github.com/apache/spark/pull/6415> to demonstrate this bug and
> discuss possible fixes. One solution might be to just revert all of the
> serializer re-use related patches until we can come up with a design
that's
> easier to prove safe.
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/spark/pull/6293#issuecomment-105612217>.
>
---
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]
