You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/04/24 21:32:00 UTC

[jira] [Work logged] (BEAM-4166) FnApiDoFnRunner doesn't invoke setup/teardown

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

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

                Author: ASF GitHub Bot
            Created on: 24/Apr/18 21:31
            Start Date: 24/Apr/18 21:31
    Worklog Time Spent: 10m 
      Work Description: jkff opened a new pull request #5216: [BEAM-4166] Invoke @Setup in FnApiDoFnRunner
URL: https://github.com/apache/beam/pull/5216
 
 
   Don't invoke Teardown because there seems to be no appropriate or necessary place to invoke it all the way up to the main() of FnHarness.
   
   R: @bsidhom 
   CC: @tgroh @angoenka 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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

            Worklog Id:     (was: 94799)
            Time Spent: 10m
    Remaining Estimate: 0h

> FnApiDoFnRunner doesn't invoke setup/teardown
> ---------------------------------------------
>
>                 Key: BEAM-4166
>                 URL: https://issues.apache.org/jira/browse/BEAM-4166
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-harness
>            Reporter: Eugene Kirpichov
>            Assignee: Eugene Kirpichov
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> And we apparently lack test coverage for that - one would think that ValidatesRunner tests would check lifecycle.



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