[
https://issues.apache.org/jira/browse/BEAM-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988702#comment-15988702
]
Aljoscha Krettek commented on BEAM-2022:
----------------------------------------
Kenn is probably talking about this method:
https://github.com/apache/beam/blob/3e243881fe767cf30869abf5c745c26f96d66fc4/runners/apex/src/main/java/org/apache/beam/runners/apex/translation/operators/ApexGroupByKeyOperator.java#L258-L258
The {{TimerData}} has a {{TimeDomain}} field (that indicates processing time,
event time, or synchronised processing time). The field is ignored and all
timers are essentially treated as event-time timers.
> ApexTimerInternals seems to treat processing time timers as event time timers
> -----------------------------------------------------------------------------
>
> Key: BEAM-2022
> URL: https://issues.apache.org/jira/browse/BEAM-2022
> Project: Beam
> Issue Type: Bug
> Components: runner-apex
> Reporter: Kenneth Knowles
> Assignee: Thomas Weise
> Fix For: First stable release
>
>
> I first noticed that {{currentProcessingTime()}} was using {{Instant.now()}},
> which has some bad issues in a distributed setting. But it seemed on
> inspection that processing time timers are simply treated as event time.
> Perhaps I am reading the code wrong?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
