SchemaIO should encode config object in the top-level schema
Open
bug
cross-language
P2
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
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.
Contributor guide
Assessment
This issue has not been assessed yet.