diff options
| author | Matt Massie <massie@cs.berkeley.edu> | 2015-09-10 17:24:33 -0700 |
|---|---|---|
| committer | Reynold Xin <rxin@databricks.com> | 2015-09-10 17:24:33 -0700 |
| commit | 0eabea8a058ad60411c1384930ba12c1c638f5f1 (patch) | |
| tree | 365097e7b2520b82e21ad019e9e543cbfe380ab0 /docs | |
| parent | 89562a172fd3efa032f60714d600407c6cfe2c2f (diff) | |
| download | spark-0eabea8a058ad60411c1384930ba12c1c638f5f1.tar.gz spark-0eabea8a058ad60411c1384930ba12c1c638f5f1.tar.bz2 spark-0eabea8a058ad60411c1384930ba12c1c638f5f1.zip | |
[SPARK-9043] Serialize key, value and combiner classes in ShuffleDependency
ShuffleManager implementations are currently not given type information for
the key, value and combiner classes. Serialization of shuffle objects relies
on objects being JavaSerializable, with methods defined for reading/writing
the object or, alternatively, serialization via Kryo which uses reflection.
Serialization systems like Avro, Thrift and Protobuf generate classes with
zero argument constructors and explicit schema information
(e.g. IndexedRecords in Avro have get, put and getSchema methods).
By serializing the key, value and combiner class names in ShuffleDependency,
shuffle implementations will have access to schema information when
registerShuffle() is called.
Author: Matt Massie <massie@cs.berkeley.edu>
Closes #7403 from massie/shuffle-classtags.
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions