[
https://issues.apache.org/jira/browse/BEAM-7948?focusedWorklogId=347237&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-347237
]
ASF GitHub Bot logged work on BEAM-7948:
----------------------------------------
Author: ASF GitHub Bot
Created on: 21/Nov/19 07:27
Start Date: 21/Nov/19 07:27
Worklog Time Spent: 10m
Work Description: sunjincheng121 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_r348928070
##########
File path:
sdks/java/fn-execution/src/main/java/org/apache/beam/sdk/fn/data/BeamFnDataTimeBasedBufferingOutboundObserver.java
##########
@@ -48,25 +46,27 @@
Coder<T> coder,
StreamObserver<BeamFnApi.Elements> outboundObserver) {
super(sizeLimit, outputLocation, coder, outboundObserver);
- this.lock = new Object();
+ this.flushLock = new Object();
this.flushFuture =
Executors.newSingleThreadScheduledExecutor(
new ThreadFactoryBuilder()
.setDaemon(true)
.setNameFormat("DataBufferOutboundFlusher-thread")
.build())
.scheduleAtFixedRate(this::periodicFlush, timeLimit, timeLimit,
TimeUnit.MILLISECONDS);
Review comment:
I found that the callable version of schedule is not a periodic action. So,
we have to create a new method which warps the `flush`, What do you think?
----------------------------------------------------------------
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: 347237)
Time Spent: 2h 40m (was: 2.5h)
> 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: 2h 40m
> 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)
