[
https://issues.apache.org/jira/browse/FLINK-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15093981#comment-15093981
]
ASF GitHub Bot commented on FLINK-3140:
---------------------------------------
Github user fhueske commented on the pull request:
https://github.com/apache/flink/pull/1465#issuecomment-170934568
Yes, I think so.
ATM, the Table API does not allow to access nested fields but only Row
fields as a whole. So there is no way to define different order for nested
types. I think we'll keep it like this for now. If we change it at some point,
we have to touch the code again.
> 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)
