You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "sunjincheng (JIRA)" <ji...@apache.org> on 2019/06/21 10:12:00 UTC
[jira] [Closed] (FLINK-12778) Fix deriveTableAggRowType bug for
non-composite types
[ https://issues.apache.org/jira/browse/FLINK-12778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
sunjincheng closed FLINK-12778.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
Fixed in master: 18dedb7749b0c8672d28dadb290d66ca3d12a87d
> Fix deriveTableAggRowType bug for non-composite types
> -----------------------------------------------------
>
> Key: FLINK-12778
> URL: https://issues.apache.org/jira/browse/FLINK-12778
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / API
> Reporter: Hequn Cheng
> Assignee: Hequn Cheng
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, we call {{aggCalls.get(0).`type`.getFieldList.foreach(builder.add)}} when derive row type for table aggregate. However, for types which are not composite types, the field list would be null. Table Aggregate should, of course, support non-composite types.
> To solve the problem, we should judge whether types are structured. This is because a composite type will be converted to a RelDataType which contains field list and is structured.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)