damccorm opened a new issue, #21160:
URL: https://github.com/apache/beam/issues/21160
Currently documentation regarding how language specific types map to Beam
schema types and vice versa are scattered in different locations.
For example,
* Following describes how Python types map to Beam schema types.
[https://beam.apache.org/releases/pydoc/2.32.0/apache_beam.typehints.schemas.html](https://beam.apache.org/releases/pydoc/2.32.0/apache_beam.typehints.schemas.html)
* Beam Programming Guides gives some details regarding types and few
examples but this seems to be incomplete.
[https://beam.apache.org/documentation/programming-guide/#schemas](https://beam.apache.org/documentation/programming-guide/#schemas)
* Following has a table that describes how types from various languages
relate to each other.
[https://docs.google.com/document/d/1uu9pJktzT_O3DxGd1-Q2op4nRk4HekIZbzi-0oTAips/edit#bookmark=id.tlciv62z2d9u](https://docs.google.com/document/d/1uu9pJktzT_O3DxGd1-Q2op4nRk4HekIZbzi-0oTAips/edit#bookmark=id.tlciv62z2d9u)
* There's limited documentation on using Python NamedTupes to properly
create Beam Rows.
Ideally, we should extend the Beam Programming Guide (or create a new guide)
to describe currently supported Schema types and how types from various SDK
languages map to such types. We should also have enough examples to illustrate
the usage.
Imported from Jira
[BEAM-13170](https://issues.apache.org/jira/browse/BEAM-13170). Original Jira
may contain additional context.
Reported by: chamikara.
--
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]
