beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Knowles (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BEAM-40) Replace rawtype lambda-incompatible uses of SerializableFunction with SimpleFunction (as appropriate)
Date Tue, 02 May 2017 20:32:04 GMT

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

Kenneth Knowles updated BEAM-40:
--------------------------------
    Fix Version/s:     (was: First stable release)
                   Not applicable

> Replace rawtype lambda-incompatible uses of SerializableFunction with SimpleFunction
(as appropriate)
> -----------------------------------------------------------------------------------------------------
>
>                 Key: BEAM-40
>                 URL: https://issues.apache.org/jira/browse/BEAM-40
>             Project: Beam
>          Issue Type: Task
>          Components: sdk-java-core
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>            Priority: Minor
>              Labels: Java8, backward-incompatible
>             Fix For: Not applicable
>
>
> When a lambda or method reference is used in Java 8 to provide a SerializableFunction<InputT,
OutputT>, it is instantiated at the raw type SerializableFunction. We occasionally require
reflective access to the actual parameter for OutputT, but it will be unavailable.
> MapElements and FlatMapElements thus use the analogous abstract class SimpleFunction
in such situations to prevent use of a lambda or method reference. They then support lambda
via separate constructors that require user help to determine the concrete output type.
> This ticket calls for an audit of such situations.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message