[
https://issues.apache.org/jira/browse/FLINK-23841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17402099#comment-17402099
]
Till Rohrmann commented on FLINK-23841:
---------------------------------------
I think the proposed change is correct. I think the idea is that
{{reigsterKryoType}} won't be registered at the POJO serializer. However a type
can still be a POJO. That's what it tries to say.
{quote} I think the typo may be obvious, however, from my understanding of
Flink and a test job. Even a pojo type registered with `registerKryoType()`, it
could still be avaiable to POJO serializer instances unless we set
`enableForceKryo`. It seems the statements of this part needs to be changed.
{quote}
I think that's what's also written in the documentation on the same page:
{quote} If the type ends up being serialized with Kryo, then it will be
registered at Kryo to make sure that only tags (integer IDs) are written. If a
type is not registered with Kryo, its entire class-name will be serialized with
every instance, leading to much higher I/O costs. {quote}
> [doc]Modify incorrect English statements for page 'execution_configuration'
> ---------------------------------------------------------------------------
>
> Key: FLINK-23841
> URL: https://issues.apache.org/jira/browse/FLINK-23841
> Project: Flink
> Issue Type: Bug
> Components: Documentation
> Reporter: wuguihu
> Priority: Minor
> Labels: pull-request-available
>
> [https://ci.apache.org/projects/flink/flink-docs-master/docs/dev/datastream/execution/execution_configuration/]
>
> The English statement in line 82 is not correct.
> {code:java}
> //line 82
> Note that types registered with `registerKryoType()` are not available to
> Flink's Kryo serializer instance.
> {code}
> It should be modified as follows:
> {code:java}
> Note that types registered with `registerKryoType()` are not available to
> Flink's POJO serializer instance.
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
