-
Notifications
You must be signed in to change notification settings - Fork 67
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
Generated client libraries don't handle proto messages with "mapping" field properly #1113
Comments
@ipotuzhnov There's no documentation nor examples on how to generate multiple language subtitles/captions so this makes implementing such a thing very difficult. The observed error can, for sure be improved, as the information provided is not very useful: Traceback (most recent call last): While facing this error, we used a python dictionary, as there's the only way we found to generate a JobConfig Object using TextStream mappings, it was very time consuming, by try an error approach. |
This is an unfortunate limitation of the Proto Plus library: PR adding |
Hi Dov, thank you for a quick fix! I hope this will land soon, so we can add examples to our client library for Python. @breogangf I understand your frustration. The API is very flexible and we can't cover all use cases, but we continuously work on improving our documentation and planning to add samples for CC/subtitle usage as well. |
TL;DR
Transcoder API uses a field named
mapping
in proto message TextStream which appears to be used in a base class for a proto message, this makes it difficult to use the client library with Transcoder API.I've noticed that for a somewhat similar case (field
type
) the autogenerated code added_
to the end of the name of the field making ittype_
, shouldn't this be done for fields namedmapping
as well?One of the Transcoder API customers reported that they were having difficulties using Python client library for Transcoder API to create a job to generate subtitles (TextStream).
Environment details
google-api-core 2.0.0
google-auth 2.0.0
google-cloud-video-transcoder 0.5.0
googleapis-common-protos 1.53.0
grpcio 1.39.0
Steps to reproduce
mapping_issue.py
Dockerfile
Workaround
Use python dictionary
The text was updated successfully, but these errors were encountered: