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

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

                Author: ASF GitHub Bot
            Created on: 14/Jun/21 07:18
            Start Date: 14/Jun/21 07:18
    Worklog Time Spent: 10m 
      Work Description: ibzib commented on pull request #14995:
URL: https://github.com/apache/beam/pull/14995#issuecomment-859726183


   LGTM, thanks for fixing this.
   
   > I did notice that Spark PVR Streaming tests have been broken into two 
tests in #14483 but not for Batch tests, are we going to apply the same 
improvement for batch mode tests ?
   
   I don't think there's much of a reason to separate them, since unlike the 
streaming tests both Spark versions consistently pass tests (while in 
streaming, Spark 3 is much less flaky than Spark 2, for unknown reasons).


-- 
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: 610110)
    Time Spent: 5h 10m  (was: 5h)

> Timeout/WaitForReady support in java gRPC calls
> -----------------------------------------------
>
>                 Key: BEAM-12419
>                 URL: https://issues.apache.org/jira/browse/BEAM-12419
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-core
>            Reporter: Ke Wu
>            Assignee: Ke Wu
>            Priority: P2
>          Time Spent: 5h 10m
>  Remaining Estimate: 0h
>
> gRPC calls in java Portable pipeline does not have retry or timeout enabled, 
> unlike python BEAM-7933
> Email discussion: 
> https://lists.apache.org/thread.html/rd4de8d54b22777913a8e20ee04e8b9d5c9aa7c16942ab36d7d168425%40%3Cdev.beam.apache.org%3E



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

Reply via email to