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 2020/09/26 17:08:03 UTC

[jira] [Commented] (BEAM-10583) Document Beam Python on Databricks

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

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

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> Document Beam Python on Databricks
> ----------------------------------
>
>                 Key: BEAM-10583
>                 URL: https://issues.apache.org/jira/browse/BEAM-10583
>             Project: Beam
>          Issue Type: Wish
>          Components: runner-spark
>            Reporter: Kyle Weaver
>            Priority: P2
>              Labels: portability-spark, stale-P2
>
> There are folks out there trying to run Beam Python on Databricks [1]. While there is documentation out there for the Java SDK [2], Python is more involved because the user needs to install the SDK harness.
> [1] [https://github.com/tensorflow/tfx/issues/2220]
> [2] [https://towardsdatascience.com/running-an-apache-beam-data-pipeline-on-azure-databricks-c09e521d8fc3]



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