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

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

                Author: ASF GitHub Bot
            Created on: 07/Nov/18 18:44
            Start Date: 07/Nov/18 18:44
    Worklog Time Spent: 10m 
      Work Description: HuangLED commented on issue #6966: [DRAFT] [BEAM-5931] 
Add worker jar to integrationTest targets.
URL: https://github.com/apache/beam/pull/6966#issuecomment-436733681
 
 
   Run Java TextIO Performance Test

----------------------------------------------------------------
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:
us...@infra.apache.org


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

    Worklog Id:     (was: 163583)
    Time Spent: 4.5h  (was: 4h 20m)

> Rollback PR/6899
> ----------------
>
>                 Key: BEAM-5931
>                 URL: https://issues.apache.org/jira/browse/BEAM-5931
>             Project: Beam
>          Issue Type: Task
>          Components: beam-model, runner-dataflow
>            Reporter: Luke Cwik
>            Assignee: Ruoyun Huang
>            Priority: Major
>          Time Spent: 4.5h
>  Remaining Estimate: 0h
>
> To rollback this change, one must either:
> 1) Update nexmark / perf test framework to use Dataflow worker jar.
> This requires adding the 
> {code}
>      "--dataflowWorkerJar=${dataflowWorkerJar}",
>      "--workerHarnessContainerImage=",
> {code}
> when running the tests.
> OR
> 2) Update the dataflow worker image with code that contains the rollback of 
> PR/6899 and then rollback PR/6899 in Github with the updated Dataflow worker 
> image.
> #1 is preferable since we will no longer have tests running that don't use a 
> Dataflow worker jar built from Github HEAD.



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

Reply via email to