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

Posted to issues@beam.apache.org by "Brian Hulette (Jira)" <ji...@apache.org> on 2022/05/04 21:02:00 UTC

[jira] [Created] (BEAM-14414) SchemaIO should encode config object in the top-level schema

Brian Hulette created BEAM-14414:
------------------------------------

             Summary: SchemaIO should encode config object in the top-level schema
                 Key: BEAM-14414
                 URL: https://issues.apache.org/jira/browse/BEAM-14414
             Project: Beam
          Issue Type: Bug
          Components: cross-language
            Reporter: Brian Hulette


The Java ExpansionService has [logic|https://github.com/apache/beam/blob/52c3f07aa56de738db3130283716d38206de42b7/sdks/java/expansion-service/src/main/java/org/apache/beam/sdk/expansion/service/ExpansionService.java#L281] for re-ordering fields based on the client's reported schema and the expanding transforms expected schema.

Currently SchemaIO bypasses this by placing the config object as encoded bytes in a field in the top-level schema. This can cause issues like BEAM-14230.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)