baeminbo opened a new issue, #35081: URL: https://github.com/apache/beam/issues/35081
### What would you like to happen? Currently, Beam Schemas generated from Protobuf Messages and Descriptors treat all fields as non-null. This is inconsistent with how optional fields in proto2/proto3 handle "presence" (whether a default value is set explicitly or not). This proposal aims to align the nullability in Beam Schemas with how Protobuf handles it. For more details, please refer to https://docs.google.com/document/d/1euOq_Uu4sycT-AiN6MQxJmsOgInyABiFSwW-U3kpwlk/edit?usp=sharing ### Issue Priority Priority: 2 (default / most feature requests 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 YAML - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] Component: Infrastructure - [ ] Component: Spark Runner - [ ] Component: Flink Runner - [ ] Component: Samza Runner - [ ] Component: Twister2 Runner - [ ] Component: Hazelcast Jet Runner - [ ] Component: Google Cloud Dataflow Runner -- 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-unsubscr...@beam.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
