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

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

                Author: ASF GitHub Bot
            Created on: 30/Mar/20 19:12
            Start Date: 30/Mar/20 19:12
    Worklog Time Spent: 10m 
      Work Description: KevinGG commented on issue #11262: [BEAM-7923] Fix 
datatable on notebook reloading
URL: https://github.com/apache/beam/pull/11262#issuecomment-606187708
 
 
   > How do you test this? Since the change is in the string template?
   
   We have the integration test in the container image release process.
   The fix doesn't affect any notebook or Beam usage.
   It only deals with browser reload of a saved notebook.
   Currently, we'll have to manually test it by reloading a browser.
 
----------------------------------------------------------------
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: 412520)
    Time Spent: 11h 50m  (was: 11h 40m)

> Interactive Beam
> ----------------
>
>                 Key: BEAM-7923
>                 URL: https://issues.apache.org/jira/browse/BEAM-7923
>             Project: Beam
>          Issue Type: New Feature
>          Components: runner-py-interactive
>            Reporter: Ning Kang
>            Assignee: Ning Kang
>            Priority: Major
>          Time Spent: 11h 50m
>  Remaining Estimate: 0h
>
> This is the top level ticket for all efforts leveraging [interactive 
> Beam|[https://github.com/apache/beam/tree/master/sdks/python/apache_beam/runners/interactive]]
> As the development goes, blocking tickets will be added to this one.
>  
>  



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

Reply via email to