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

   ### What would you like to happen?
   
   In 
[WriteToPubSubLite](https://beam.apache.org/releases/yamldoc/current/#writetopubsublite)
 it supports `PROTO`:
   
   > format string : The encoding format for the data stored in Pubsub Lite. 
Valid options are: RAW,JSON,AVRO,PROTO
   
   But in 
[WriteToPubSub](https://beam.apache.org/releases/yamldoc/current/#writetopubsub)
 it does not:
   
   > format string : How to format the message payload. Currently suported 
formats are
   >> RAW: Expects a message with a single field (excluding attribute-related 
fields) whose contents are used as the raw bytes of the pubsub message.
   >> AVRO: Encodes records with a given Avro schema, which may be inferred 
from the input PCollection schema.
   >> JSON: Formats records with a given JSON schema, which may be inferred 
from the input PCollection schema.
   
   Is it possible to add support for `PROTO` when writing to Pub/Sub?
   
   Is there an existing workaround?
   
   ### Issue Priority
   
   Priority: 2 (default / most feature requests should be filed as P2)
   
   ### Issue Components
   
   - [ ] Component: Python SDK
   - [ ] Component: Java SDK
   - [ ] Component: Go SDK
   - [ ] Component: Typescript SDK
   - [ ] Component: IO connector
   - [x] 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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to