[
https://issues.apache.org/jira/browse/FLINK-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15062141#comment-15062141
]
ASF GitHub Bot commented on FLINK-3140:
---------------------------------------
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/1465#issuecomment-165474222
@aljoscha is absolutely right about the performance aspect. However, the
key difference is that he was referring in his comment to the implementation of
the `serialize` method which is extensively used and, thus, should be as
efficient as possible.
If I'm not mistaken, then this argument does not apply to the
`createAuxiliaryFields` method, though. The reason is that this method is
called before the job is actually executed and, consequently, should not have
any impact on the runtime behaviour. But I might be wrong here, since we're
also shipping `TypeInformation` to the cluster, nowadays.
> NULL value data layout in Row Serializer/Comparator
> ---------------------------------------------------
>
> Key: FLINK-3140
> URL: https://issues.apache.org/jira/browse/FLINK-3140
> Project: Flink
> Issue Type: Sub-task
> Components: Table API
> Reporter: Chengxiang Li
> Assignee: Timo Walther
>
> To store/materialize NULL value in Row objects, we should need new Row
> Serializer/Comparator which is aware of NULL value fields.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
