[
https://issues.apache.org/jira/browse/FLINK-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328678#comment-17328678
]
Flink Jira Bot commented on FLINK-8379:
---------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> Improve type checking for DataView
> ----------------------------------
>
> Key: FLINK-8379
> URL: https://issues.apache.org/jira/browse/FLINK-8379
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Reporter: Timo Walther
> Priority: Major
> Labels: stale-major
>
> At the moment an accumulator with no proper type information is a valid
> accumulator.
> {code}
> public static class CountDistinctAccum {
> public MapView<Tuple, Integer> map;
> public long count;
> }
> {code}
> I quickly looked into the code and it seems that MapView with type
> information for key and value can be null. We should add a null check at the
> correct position to inform the user about the non-existing type information.
> We should also add the type check added with FLINK-8139 for the key type of
> MapView.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
