JanusGraph/janusgraph

Kryo registrator options for Spark

開放

#1,194 建立於 2018年7月27日

 (2 則留言) (0 個反應) (0 位負責人)Java (1,137 個分叉)batch import
area/docsarea/sparkhelp wantedkind/enhancement

倉庫指標

星標
 (4,985 顆星)
PR 合併指標
 (平均合併 3天 18小時) (30 天內合併 12 個 PR)

描述

This came up during a documentation review:

https://github.com/JanusGraph/janusgraph/blob/0.2/janusgraph-hadoop-parent/janusgraph-hadoop-core/src/test/resources/cassandra-read.properties#L30 Should we use:

spark.kryo.registrator=org.janusgraph.hadoop.serialize.JanusGraphKryoRegistrator

Or:

spark.kryo.registrator=org.apache.tinkerpop.gremlin.spark.structure.io.gryo.GryoRegistrator

JanusGraphKryoRegistrator only registers a serializer for Geoshape, while the TinkerPop GryoRegistrator handles many different classes. JanusGraphKryoRegistrator does not extend GryoRegistrator.

We need some clarity on how to configure the Kryo registrator to cover all required TinkerPop and JanusGraph classes. Also will need updates on the documentation and the properties files in the distribution.

貢獻者指南