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

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

                Author: ASF GitHub Bot
            Created on: 04/Dec/19 00:14
            Start Date: 04/Dec/19 00:14
    Worklog Time Spent: 10m 
      Work Description: KevinGG commented on pull request #10276: [BEAM-7926] 
Data-centric Interactive Part1
URL: https://github.com/apache/beam/pull/10276#discussion_r353490527
 
 

 ##########
 File path: 
sdks/python/apache_beam/runners/interactive/interactive_environment.py
 ##########
 @@ -221,3 +224,20 @@ def is_terminated(self, pipeline):
     if result:
       return runner.PipelineState.is_terminal(result.state)
     return True
+
+  def track_user_pipelines(self):
+    """Tracks all user-defined pipeline instances.
 
 Review comment:
   Rephrasing to
   ```
       """Record references to all user-defined pipeline instances watched in
       current environment.
   
       Current static global singleton interactive environment holds references 
to
       a set of pipeline instances defined by the user in the watched scope.
       Interactive Beam features could use the references to determine if a 
given
       pipeline is defined by user or implicitly created by Beam SDK or runners,
       then handle them differently.
   
       This is invoked every time a PTransform is to be applied if the current
       code execution is under ipython due to the possibility that any 
user-defined
       pipeline can be re-evaluated through notebook cell re-execution at any 
time.
   
       Each time this is invoked, the tracked user pipelines are refreshed to
       remove any pipeline instances that are no longer in watched scope. For
       example, after a notebook cell re-execution re-evaluating a pipeline
       creation, the last pipeline reference created by last evaluation will 
not be
       in watched scope anymore.
       """
   ```
 
----------------------------------------------------------------
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:
us...@infra.apache.org


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

    Worklog Id:     (was: 353130)
    Time Spent: 22h 40m  (was: 22.5h)

> Show PCollection with Interactive Beam in a data-centric user flow
> ------------------------------------------------------------------
>
>                 Key: BEAM-7926
>                 URL: https://issues.apache.org/jira/browse/BEAM-7926
>             Project: Beam
>          Issue Type: New Feature
>          Components: runner-py-interactive
>            Reporter: Ning Kang
>            Assignee: Ning Kang
>            Priority: Major
>          Time Spent: 22h 40m
>  Remaining Estimate: 0h
>
> Support auto plotting / charting of materialized data of a given PCollection 
> with Interactive Beam.
> Say an Interactive Beam pipeline defined as
>  
> {code:java}
> p = beam.Pipeline(InteractiveRunner())
> pcoll = p | 'Transform' >> transform()
> pcoll2 = ...
> pcoll3 = ...{code}
> The use can call a single function and get auto-magical charting of the data.
> e.g.,
> {code:java}
> show(pcoll, pcoll2)
> {code}
> Throughout the process, a pipeline fragment is built to include only 
> transforms necessary to produce the desired pcolls (pcoll and pcoll2) and 
> execute that fragment.
> This makes the Interactive Beam user flow data-centric.
>  
> Detailed 
> [design|https://docs.google.com/document/d/1DYWrT6GL_qDCXhRMoxpjinlVAfHeVilK5Mtf8gO6zxQ/edit#heading=h.v6k2o3roarzz].



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

Reply via email to