GitHub user mhseiden opened a pull request:
https://github.com/apache/spark/pull/5237
[SPARK-5277][SQL] - SparkSqlSerializer doesn't always register user
specified KryoRegistrators
[SPARK-5277][SQL] - SparkSqlSerializer doesn't always register user
specified KryoRegistrators
There were a few places where new SparkSqlSerializer instances were created
with new, empty SparkConfs resulting in user specified registrators sometimes
not getting initialized.
The fix is to try and pull a conf from the SparkEnv, and construct a new
conf (that loads defaults) if one cannot be found.
The changes touched:
1) SparkSqlSerializer's resource pool (this appears to fix the issue in
the comment)
2) execution.Exchange (for all of the partitioners)
3) execution.Limit (for the HashPartitioner)
A few tests were added to ColumnTypeSuite, ensuring that a custom
registrator and serde is initialized and used when in-memory columns are
written.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mhseiden/spark sql_udt_kryo
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/5237.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5237
----
commit e5011fbc77019291ce76cca004b9ac5839dc59d0
Author: Max Seiden <[email protected]>
Date: 2015-03-28T06:40:16Z
[SPARK-5277][SQL] - SparkSqlSerializer does not register user specified
KryoRegistrators
There were a few places where new SparkSqlSerializer instances were created
with new, empty SparkConfs resulting in user specified registrators sometimes
not getting initialized.
The fix is to try and pull a conf from the SparkEnv, and construct a new
conf (that loads default) if one cannot be found.
The changes touched:
1) SparkSqlSerializer's resource pool (this appears to fix the issue in
the comment)
2) execution.Exchange (for all of the partitioners)
3) execution.Limit (for the HashPartitioner)
A few tests were added to ColumnTypeSuite, ensuring that a custom
registrator and serde is initialized and used when in-memory columns are
written.
----
---
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]
