[
https://issues.apache.org/jira/browse/BEAM-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16841777#comment-16841777
]
Reuven Lax commented on BEAM-7116:
----------------------------------
The problem is that Beam special cases KvCoder all over the place, so if we
cause KV to use SchemaCoder we will break large parts of Beam. I think it
will be easier to just remove KV from our interface and let any two-field
schema translate to KV.
However what you suggested is indeed a problem in Schema type inference -
we don't do a good job with generic classes (someone trying AutoValueSchema
hit this). Do you want to file a JIRA for this issue, as there doesn't
appear to be one?
*From: *Brian Hulette (JIRA) <[email protected]>
*Date: *Thu, May 16, 2019 at 1:38 PM
*To: * <[email protected]>
> Remove KV from Schema transforms
> --------------------------------
>
> Key: BEAM-7116
> URL: https://issues.apache.org/jira/browse/BEAM-7116
> Project: Beam
> Issue Type: Sub-task
> Components: sdk-java-core
> Reporter: Reuven Lax
> Priority: Major
>
> Instead of returning KV objects, we should return a Schema with two fields.
> The Convert transform should be able to convert these to KV objects.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
