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

Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/06/05 00:19:14 UTC

[GitHub] [beam] damccorm opened a new issue, #21552: SchemaIO should encode config object in the top-level schema

damccorm opened a new issue, #21552:
URL: https://github.com/apache/beam/issues/21552

   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.
   
   Imported from Jira [BEAM-14414](https://issues.apache.org/jira/browse/BEAM-14414). Original Jira may contain additional context.
   Reported by: bhulette.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org