[
https://issues.apache.org/jira/browse/FLINK-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15743965#comment-15743965
]
Jark Wu commented on FLINK-5280:
--------------------------------
Hi [~ivan.mushketyk], I will try to answer your question.
The main problem you confused is that {{CodeGenerator}} doesn't support nested
access. Actually, it has been fixed in FLINK-4294, and you can have a look at
the test example {{CompositeAccessTest}}. I think it will give you some
inspiration.
And the other problem that {{BatchScan#convertToExpectedType}} will convert
input dataset into Row type. Actually, it will not flatten the nested fields,
but keep the same schema in Row. In your case, the ParentPojo will be
converted Row type with {{Row(child: ChildPojo, num:Int)}}.
Hope that will help you.
> Extend TableSource to support nested data
> -----------------------------------------
>
> Key: FLINK-5280
> URL: https://issues.apache.org/jira/browse/FLINK-5280
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Affects Versions: 1.2.0
> Reporter: Fabian Hueske
> Assignee: Ivan Mushketyk
>
> The {{TableSource}} interface does currently only support the definition of
> flat rows.
> However, there are several storage formats for nested data that should be
> supported such as Avro, Json, Parquet, and Orc. The Table API and SQL can
> also natively handle nested rows.
> The {{TableSource}} interface and the code to register table sources in
> Calcite's schema need to be extended to support nested data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
