You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Dominik Wosiński (JIRA)" <ji...@apache.org> on 2019/04/29 14:20:00 UTC

[jira] [Updated] (FLINK-12367) Create rich versions of functions for Scala

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

Dominik Wosiński updated FLINK-12367:
-------------------------------------
    Description: 
Currently for some of the functions like for example _AsyncFunctions_ have their rich versions available only for Java, which makes using them more complicated to use in Scala. For example using _RichAsyncFunction_ that allows state for example requires a lot of changes, since AFAIK it will not normally work with _DataStream_ from scala API. This will force user to make various changes in the code to be compatible with the API_._ This also includes the fact that the variance is different for Scala and Java collections, since the former ones are covariant by default and the latter ones are invariant by default.

 

 

  was:Currently for some of the functions like for example _AsyncFunctions_ have their rich versions available only for Java, which makes using them more complicated to use in Scala. For example using _RichAsyncFunction_ that allows state for example requires a lot of changes, since AFAIK it will not normally work with _DataStream_ from scala API. This will force user to make various changes in the code to be compatible with the API.


> Create rich versions of functions for Scala
> -------------------------------------------
>
>                 Key: FLINK-12367
>                 URL: https://issues.apache.org/jira/browse/FLINK-12367
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: Dominik Wosiński
>            Assignee: Dominik Wosiński
>            Priority: Major
>
> Currently for some of the functions like for example _AsyncFunctions_ have their rich versions available only for Java, which makes using them more complicated to use in Scala. For example using _RichAsyncFunction_ that allows state for example requires a lot of changes, since AFAIK it will not normally work with _DataStream_ from scala API. This will force user to make various changes in the code to be compatible with the API_._ This also includes the fact that the variance is different for Scala and Java collections, since the former ones are covariant by default and the latter ones are invariant by default.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)