You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2015/06/23 10:26:00 UTC

[jira] [Updated] (FLINK-2197) Scala API is not working when using batch and streaming API in the same program

     [ https://issues.apache.org/jira/browse/FLINK-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann updated FLINK-2197:
---------------------------------
    Description: If one uses the the Scala batch and streaming API from within the same program and imports both corresponding package objects, then the Scala API no longer works because it is lacking the implicit {{TypeInformation}} values. The reason for this is that both package objects contain an implicit function {{createTypeInformation}}. This creates an ambiguity which is not possible for the Scala compiler to resolve.  (was: If one uses the the Scala batch and streaming API from within the same program and imports both corresponding package objects, then the Scala API no longer works because it is lacking the implicit {{TypeInformation}} values. The reason for this is that both package objects contain an implicit function {createTypeInformation}}. This creates an ambiguity which is not possible for the Scala compiler to resolve.)

> Scala API is not working when using batch and streaming API in the same program
> -------------------------------------------------------------------------------
>
>                 Key: FLINK-2197
>                 URL: https://issues.apache.org/jira/browse/FLINK-2197
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Till Rohrmann
>
> If one uses the the Scala batch and streaming API from within the same program and imports both corresponding package objects, then the Scala API no longer works because it is lacking the implicit {{TypeInformation}} values. The reason for this is that both package objects contain an implicit function {{createTypeInformation}}. This creates an ambiguity which is not possible for the Scala compiler to resolve.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)