[
https://issues.apache.org/jira/browse/FLINK-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534457#comment-14534457
]
ASF GitHub Bot commented on FLINK-1676:
---------------------------------------
Github user rmetzger commented on a diff in the pull request:
https://github.com/apache/flink/pull/473#discussion_r29937747
--- Diff:
flink-java/src/main/java/org/apache/flink/api/java/typeutils/GenericTypeInfo.java
---
@@ -70,9 +69,6 @@ public boolean isKeyType() {
@Override
public TypeSerializer<T> createSerializer(ExecutionConfig config) {
- if(config.serializeGenericTypesWithAvro()) {
--- End diff --
POJOs generated by Avro will be handled by the Avro serializer
Generic Types always with Kryo serializer
This change allows to force the POJO serializer to serialize the ENTIRE
pojo with Kryo or Avro.
I added a section in the documentation explaining the settings.
> enableForceKryo() is not working as expected
> --------------------------------------------
>
> Key: FLINK-1676
> URL: https://issues.apache.org/jira/browse/FLINK-1676
> Project: Flink
> Issue Type: Bug
> Components: Java API
> Affects Versions: 0.9
> Reporter: Robert Metzger
>
> I my Flink job, I've set the following execution config
> {code}
> final ExecutionEnvironment env =
> ExecutionEnvironment.getExecutionEnvironment();
> env.getConfig().disableObjectReuse();
> env.getConfig().enableForceKryo();
> {code}
> Setting a breakpoint in the {{PojoSerializer()}} constructor, you'll see that
> we still serialize data with the POJO serializer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
