zentol commented on a change in pull request #8352: [hotfix][docs] mention kryo in serialization and link to page URL: https://github.com/apache/flink/pull/8352#discussion_r284595653
########## File path: docs/dev/types_serialization.md ########## @@ -281,21 +281,21 @@ by all compilers (as of writing this document only reliably by the Eclipse JDT c #### Serialization of POJO types -The PojoTypeInformation is creating serializers for all the fields inside the POJO. Standard types such as +The `PojoTypeInfo` is creating serializers for all the fields inside the POJO. Standard types such as int, long, String etc. are handled by serializers we ship with Flink. -For all other types, we fall back to Kryo. +For all other types, we fall back to [Kryo](https://github.com/EsotericSoftware/kryo). -If Kryo is not able to handle the type, you can ask the PojoTypeInfo to serialize the POJO using Avro. +If Kryo is not able to handle the type, you can ask the `PojoTypeInfo` to serialize the POJO using [Avro](http://avro.apache.org). To do so, you have to call {% highlight java %} final ExecutionEnvironment env = ExecutionEnvironment.getExecutionEnvironment(); env.getConfig().enableForceAvro(); {% endhighlight %} -Note that Flink is automatically serializing POJOs generated by Avro with the Avro serializer. +Note that Flink is automatically serializing POJOs generated by Avro with the `AvroSerializer`. Review comment: this change seems unnecessary, we don't _have_ to refer to classes. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
