You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/11/25 17:12:01 UTC

[jira] [Commented] (BEAM-10765) Support non-homogenous nested types in SchemaProvider implementations

    [ https://issues.apache.org/jira/browse/BEAM-10765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238820#comment-17238820 ] 

Beam JIRA Bot commented on BEAM-10765:
--------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> Support non-homogenous nested types in SchemaProvider implementations
> ---------------------------------------------------------------------
>
>                 Key: BEAM-10765
>                 URL: https://issues.apache.org/jira/browse/BEAM-10765
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Brian Hulette
>            Priority: P2
>              Labels: Clarified, stale-P2
>
> Currently we can infer schemas for nested types, but only when they are homogenous (e.g. an AutoValue with an AutoValue field, or a Java Bean with a Java Bean field). 
> We should also support schema inference for non-homogenous types, so that schemas can be inferred for an AutoValue field with a Java Bean field.
> Not doing so can lead to confusing errors like the one reported in https://lists.apache.org/thread.html/rc7c45ff8efd425fe545b6020c5b4250c99f6c788bf32a114708187a1%40%3Cuser.beam.apache.org%3E



--
This message was sent by Atlassian Jira
(v8.3.4#803005)