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

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

                Author: ASF GitHub Bot
            Created on: 10/May/19 22:40
            Start Date: 10/May/19 22:40
    Worklog Time Spent: 10m 
      Work Description: aaltay commented on issue #7994: [BEAM-562] Add 
DoFn.setup and DoFn.teardown to Python SDK
URL: https://github.com/apache/beam/pull/7994#issuecomment-491449676
 
 
   > The shutdown assert is breaking in Dataflow also (because it only works 
for in-process). Can I delete that assert, or disable it for Dataflow?
   Let's delete it. I do not think it will be easy to assert just for Dataflow 
runner.
 
----------------------------------------------------------------
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: 240458)
    Time Spent: 9h 40m  (was: 9.5h)

> DoFn Reuse: Add new methods to DoFn
> -----------------------------------
>
>                 Key: BEAM-562
>                 URL: https://issues.apache.org/jira/browse/BEAM-562
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-py-core
>            Reporter: Ahmet Altay
>            Assignee: Yifan Mai
>            Priority: Major
>              Labels: sdk-consistency
>          Time Spent: 9h 40m
>  Remaining Estimate: 0h
>
> Java SDK added setup and teardown methods to the DoFns. This makes DoFns 
> reusable and provide performance improvements. Python SDK should add support 
> for these new DoFn methods:
> Proposal doc: 
> https://docs.google.com/document/d/1LLQqggSePURt3XavKBGV7SZJYQ4NW8yCu63lBchzMRk/edit?ts=5771458f#



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to