[
https://issues.apache.org/jira/browse/FLINK-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191349#comment-15191349
]
ASF GitHub Bot commented on FLINK-1159:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1704#issuecomment-195491606
This pull request adds a lot of tests (which is actually good), but all
tests fire up a cluster to execute many programs. But need to somehow get this
down, as these "fire up mini cluster" tests have made our build times explode.
Is actual program execution needed here? Or is it sufficient to see that
the partial function for a certain transformation creates such a transformation?
> Case style anonymous functions not supported by Scala API
> ---------------------------------------------------------
>
> Key: FLINK-1159
> URL: https://issues.apache.org/jira/browse/FLINK-1159
> Project: Flink
> Issue Type: Bug
> Components: Scala API
> Reporter: Till Rohrmann
> Assignee: Stefano Baghino
>
> In Scala it is very common to define anonymous functions of the following form
> {code}
> {
> case foo: Bar => foobar(foo)
> case _ => throw new RuntimeException()
> }
> {code}
> These case style anonymous functions are not supported yet by the Scala API.
> Thus, one has to write redundant code to name the function parameter.
> What works is the following pattern, but it is not intuitive for someone
> coming from Scala:
> {code}
> dataset.map{
> _ match{
> case foo:Bar => ...
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
