3rd Party Serializers

If you use a custom type in your Flink program which cannot be serialized by the Flink type serializer, Flink falls back to using the generic Kryo serializer. You may register your own serializer or a serialization system like Google Protobuf or Apache Thrift with Kryo. To do that, simply register the type class and the serializer in the ExecutionConfig of your Flink program.

  1. final ExecutionEnvironment env = ExecutionEnvironment.getExecutionEnvironment();
  3. // register the class of the serializer as serializer for a type
  4. env.getConfig().registerTypeWithKryoSerializer(MyCustomType.class, MyCustomSerializer.class);
  6. // register an instance as serializer for a type
  7. MySerializer mySerializer = new MySerializer();
  8. env.getConfig().registerTypeWithKryoSerializer(MyCustomType.class, mySerializer);

Note that your custom serializer has to extend Kryo’s Serializer class. In the case of Google Protobuf or Apache Thrift, this has already been done for you:

  2. final StreamExecutionEnvironment env = StreamExecutionEnvironment.getExecutionEnvironment();
  4. // register the Google Protobuf serializer with Kryo
  5. env.getConfig().registerTypeWithKryoSerializer(MyCustomType.class, ProtobufSerializer.class);
  7. // register the serializer included with Apache Thrift as the standard serializer
  8. // TBaseSerializer states it should be initialized as a default Kryo serializer
  9. env.getConfig().addDefaultKryoSerializer(MyCustomType.class, TBaseSerializer.class);

For the above example to work, you need to include the necessary dependencies in your Maven project file (pom.xml). In the dependency section, add the following for Apache Thrift:

  2. <dependency>
  3.     <groupId>com.twitter</groupId>
  4.     <artifactId>chill-thrift</artifactId>
  5.     <version>0.7.6</version>
  6.     <!-- exclusions for dependency conversion -->
  7.     <exclusions>
  8.         <exclusion>
  9.             <groupId>com.esotericsoftware.kryo</groupId>
  10.             <artifactId>kryo</artifactId>
  11.         </exclusion>
  12.     </exclusions>
  13. </dependency>
  14. <!-- libthrift is required by chill-thrift -->
  15. <dependency>
  16.     <groupId>org.apache.thrift</groupId>
  17.     <artifactId>libthrift</artifactId>
  18.     <version>0.11.0</version>
  19.     <exclusions>
  20.         <exclusion>
  21.             <groupId>javax.servlet</groupId>
  22.             <artifactId>servlet-api</artifactId>
  23.         </exclusion>
  24.         <exclusion>
  25.             <groupId>org.apache.httpcomponents</groupId>
  26.             <artifactId>httpclient</artifactId>
  27.         </exclusion>
  28.     </exclusions>
  29. </dependency>

For Google Protobuf you need the following Maven dependency:

  2. <dependency>
  3.     <groupId>com.twitter</groupId>
  4.     <artifactId>chill-protobuf</artifactId>
  5.     <version>0.7.6</version>
  6.     <!-- exclusions for dependency conversion -->
  7.     <exclusions>
  8.         <exclusion>
  9.             <groupId>com.esotericsoftware.kryo</groupId>
  10.             <artifactId>kryo</artifactId>
  11.         </exclusion>
  12.     </exclusions>
  13. </dependency>
  14. <!-- We need protobuf for chill-protobuf -->
  15. <dependency>
  16.     <groupId>com.google.protobuf</groupId>
  17.     <artifactId>protobuf-java</artifactId>
  18.     <version>3.7.0</version>
  19. </dependency>

Please adjust the versions of both libraries as needed.

Issue with using Kryo’s JavaSerializer

If you register Kryo’s JavaSerializer for your custom type, you may encounter ClassNotFoundExceptions even though your custom type class is included in the submitted user code jar. This is due to a know issue with Kryo’s JavaSerializer, which may incorrectly use the wrong classloader.

In this case, you should use org.apache.flink.api.java.typeutils.runtime.kryo.JavaSerializer instead to resolve the issue. This is a reimplemented JavaSerializer in Flink that makes sure the user code classloader is used.

Please refer to FLINK-6025 for more details.