[Bug]: Schema providers of different types don't nest.
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
### What happened?
For example, if I have a class annotated with `@DefaultSchema(AutoValueSchema.class)` and it contains a field that is annotated with `@DefaultSchema(JavaFieldSchema.class)` it will claim that field has a row type with no fields.
One should be able to nest and re-use schema-aware classes without having to know or worry about how they're constructed, or at the very least this should be a clear error rather than a silent dropping of all fields.
### Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
### Issue Components
- [ ] Component: Python SDK
- [X] Component: Java SDK
- [ ] Component: Go SDK
- [ ] Component: Typescript SDK
- [ ] Component: IO connector
- [ ] Component: Beam examples
- [ ] Component: Beam playground
- [ ] Component: Beam katas
- [ ] Component: Website
- [ ] Component: Spark Runner
- [ ] Component: Flink Runner
- [ ] Component: Samza Runner
- [ ] Component: Twister2 Runner
- [ ] Component: Hazelcast Jet Runner
- [ ] Component: Google Cloud Dataflow Runner
Contributor guide
Assessment
This issue has not been assessed yet.