[
https://issues.apache.org/jira/browse/FLINK-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14517571#comment-14517571
]
ASF GitHub Bot commented on FLINK-1676:
---------------------------------------
Github user StephanEwen commented on a diff in the pull request:
https://github.com/apache/flink/pull/473#discussion_r29271929
--- Diff:
flink-java/src/main/java/org/apache/flink/api/java/typeutils/PojoTypeInfo.java
---
@@ -310,6 +316,18 @@ public int getFieldIndex(String fieldName) {
@Override
public TypeSerializer<T> createSerializer(ExecutionConfig config) {
+ if(config.isForceKryoEnabled() && config.isForceAvroEnabled()) {
--- End diff --
I don't think that the TypeInfo is the right place to log. This is going to
flood your log with 500 identical log messages for larger jobs.
> 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)
