[
https://issues.apache.org/jira/browse/FLINK-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185275#comment-14185275
]
Aljoscha Krettek commented on FLINK-1191:
-----------------------------------------
Yes, I was aware of the problem. Some special Scala types, such as Option and
Either are also not usable.
I have a branch where I work on addressing these issues:
https://github.com/aljoscha/incubator-flink/tree/scala-collections-support.
> TypeAnalyzer MatchError when analyzing BitSet type with Scala API
> -----------------------------------------------------------------
>
> Key: FLINK-1191
> URL: https://issues.apache.org/jira/browse/FLINK-1191
> Project: Flink
> Issue Type: Bug
> Reporter: Till Rohrmann
> Assignee: Aljoscha Krettek
>
> The type analyzer of the ScalaAPI treats BitSet as a ListType. When the
> unapply method of the ListType is called with a BitSet type then it will be
> considered a TraversableType. However, within the TraversableType unapply
> method there is an non-exhaustive pattern matching which fails with BitSet.
> There is also a comment which says "TODO: make sure this works as it should".
> As a result, the user only sees that some implicit evidence parameters of
> type TypeInformation are missing, because they weren't generated. From the
> user perspective, it would be nice to receive a more meaningful error message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
