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

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

                Author: ASF GitHub Bot
            Created on: 21/Nov/19 23:43
            Start Date: 21/Nov/19 23:43
    Worklog Time Spent: 10m 
      Work Description: lukecwik commented on pull request #9949: [BEAM-7948] 
Add time-based cache threshold support in the Java data s…
URL: https://github.com/apache/beam/pull/9949#discussion_r349372594
 
 

 ##########
 File path: 
sdks/java/fn-execution/src/main/java/org/apache/beam/sdk/fn/data/BeamFnDataSizeBasedBufferingOutboundObserver.java
 ##########
 @@ -85,7 +85,7 @@ public void close() throws Exception {
   }
 
   @Override
-  public void flush() throws IOException {
+  public synchronized void flush() throws IOException {
 
 Review comment:
   We don't want to make this synchronized since this class is not thread safe 
and should not take this perf hit. Your previous usage of defining an override 
that is synchronized for the class that called super.flush() is all you need.
 
----------------------------------------------------------------
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: 347796)

> Add time-based cache threshold support in the Java data service
> ---------------------------------------------------------------
>
>                 Key: BEAM-7948
>                 URL: https://issues.apache.org/jira/browse/BEAM-7948
>             Project: Beam
>          Issue Type: Sub-task
>          Components: java-fn-execution
>            Reporter: sunjincheng
>            Assignee: sunjincheng
>            Priority: Major
>          Time Spent: 3h
>  Remaining Estimate: 0h
>
> Currently only size-based cache threshold is supported in data service. It 
> should also support the time-based cache threshold. This is very important, 
> especially for streaming jobs which are sensitive to the delay.



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

Reply via email to