[
https://issues.apache.org/jira/browse/FLINK-11200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770716#comment-16770716
]
Hequn Cheng commented on FLINK-11200:
-------------------------------------
[~twalthr] Hi, Would you be ok if I port all these DataView classes into
flink-common? I failed to find a clean way to avoid porting
{{ListViewTypeInfo}} and {{ListViewSerializer}}. The reason is {{ListView}} use
{{ListViewTypeInfoFactory}} to create TypeInformation which introduces
transitive class dependencies. Unless we find a new way to define
TypeInformation similar to @TypeInfo , but it may also make things complicated.
What do you think?
> Port DataView classes to flink-table-common
> -------------------------------------------
>
> Key: FLINK-11200
> URL: https://issues.apache.org/jira/browse/FLINK-11200
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Reporter: Timo Walther
> Assignee: Hequn Cheng
> Priority: Major
>
> {{DataView}} are used within aggregate functions for more efficient state
> management. Logically, they should have been ported in FLINK-10689.
> This issue only includes {{org.apache.flink.table.api.dataview.*}} and
> {{org.apache.flink.table.dataview.StateListView/StateMapView}}. The latter
> one is shared between planning and runtime phase.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
