Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Schema providers of different types don't nest. #27983

Open
1 of 15 tasks
robertwb opened this issue Aug 12, 2023 · 0 comments
Open
1 of 15 tasks

[Bug]: Schema providers of different types don't nest. #27983

robertwb opened this issue Aug 12, 2023 · 0 comments

Comments

@robertwb
Copy link
Contributor

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
  • 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant