You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/11/04 17:26:01 UTC

[jira] [Commented] (BEAM-13002) Update to_dataframe API Docs to focus on schema use

    [ https://issues.apache.org/jira/browse/BEAM-13002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17438856#comment-17438856 ] 

Beam JIRA Bot commented on BEAM-13002:
--------------------------------------

This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.

> Update to_dataframe API Docs to focus on schema use
> ---------------------------------------------------
>
>                 Key: BEAM-13002
>                 URL: https://issues.apache.org/jira/browse/BEAM-13002
>             Project: Beam
>          Issue Type: Task
>          Components: dsl-dataframe
>            Reporter: Brian Hulette
>            Assignee: Brian Hulette
>            Priority: P2
>              Labels: stale-assigned
>
> The API documentation for to_dataframe (https://beam.apache.org/releases/pydoc/2.32.0/apache_beam.dataframe.convert.html#apache_beam.dataframe.convert.to_dataframe) is very sparse. It also focuses on specifying a proxy, rather than relying a schema-aware PCollection as an input. This function is often people's entrypoint into the API, so we should make it very clear how to use it. Let's expand the documentation, and focus on using schemas rather than specifying a proxy.
> We should also link to the documentation for to_dataframe in https://beam.apache.org/documentation/dsls/dataframes/overview/#embedding-dataframes-in-a-pipeline



--
This message was sent by Atlassian Jira
(v8.3.4#803005)