[ 
https://issues.apache.org/jira/browse/BEAM-8451?focusedWorklogId=446988&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-446988
 ]

ASF GitHub Bot logged work on BEAM-8451:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 17/Jun/20 00:47
            Start Date: 17/Jun/20 00:47
    Worklog Time Spent: 10m 
      Work Description: rosetn commented on a change in pull request #11706:
URL: https://github.com/apache/beam/pull/11706#discussion_r441217968



##########
File path: website/www/site/content/en/documentation/runners/direct.md
##########
@@ -74,55 +74,65 @@ Local execution is limited by the memory available in your 
local environment. It
 
 If your pipeline uses an unbounded data source or sink, you must set the 
`streaming` option to `true`.
 
+{:.language-py}
 ### Execution Mode
 
+{:.language-py}
 Python 
[FnApiRunner](https://beam.apache.org/contribute/runner-guide/#the-fn-api) 
supports multi-threading and multi-processing mode.
 
+{:.language-py}
 <strong>Setting parallelism</strong>
 
+{:.language-py}
 Number of threads or subprocesses is defined by setting the 
`direct_num_workers` option. 
 From 2.22.0, `direct_num_workers = 0` is supported. When `direct_num_workers` 
is set to 0, it will set the number of threads/subprocess to the number of 
cores of the machine where the pipelien is running.

Review comment:
       Sorry, this is outside of the diff, but can you change 
"pipelien"->"pipeline"




----------------------------------------------------------------
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.

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


Issue Time Tracking
-------------------

    Worklog Id:     (was: 446988)
    Time Spent: 2h 40m  (was: 2.5h)

> Interactive Beam example failing from stack overflow
> ----------------------------------------------------
>
>                 Key: BEAM-8451
>                 URL: https://issues.apache.org/jira/browse/BEAM-8451
>             Project: Beam
>          Issue Type: Bug
>          Components: examples-python, runner-py-interactive
>            Reporter: Igor Durovic
>            Assignee: Chun Yang
>            Priority: P2
>             Fix For: 2.18.0
>
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
>  
> RecursionError: maximum recursion depth exceeded in __instancecheck__
> at 
> [https://github.com/apache/beam/blob/master/sdks/python/apache_beam/runners/interactive/pipeline_analyzer.py#L405]
>  
> This occurred after the execution of the last cell in 
> [https://github.com/apache/beam/blob/master/sdks/python/apache_beam/runners/interactive/examples/Interactive%20Beam%20Example.ipynb]



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

Reply via email to