beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Halperin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BEAM-328) Provide a fallback SerializableCoder for `T extends Serializable` by default
Date Thu, 20 Oct 2016 18:04:58 GMT

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

Daniel Halperin updated BEAM-328:
---------------------------------
    Summary: Provide a fallback SerializableCoder for `T extends Serializable` by default
 (was: CoderRegistry does not provide SerializableCoder for `T extends Serializable`)

> Provide a fallback SerializableCoder for `T extends Serializable` by default
> ----------------------------------------------------------------------------
>
>                 Key: BEAM-328
>                 URL: https://issues.apache.org/jira/browse/BEAM-328
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Kenneth Knowles
>            Assignee: Manu Zhang
>            Priority: Minor
>              Labels: starter
>
> When the type for which a coder is being inferred is a type variable with an upper bound
of {{Serializable}}, it is reasonable for the coder registry to propagate this to the {{SerializableCoder.PROVIDER}},
which should be able to succeed.
> Unfortunately, the particulars of the distinctions made between {{Type}}, {{Class}},
{{TypeVariable}}, {{ParameterizedType}}, etc, go down a code path where this is not the case.
Instead, an error is raised that the type variable has been subject to erasure.
> Originally reported at: https://github.com/GoogleCloudPlatform/DataflowJavaSDK/issues/298



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

Mime
View raw message