You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Daniel Halperin (JIRA)" <ji...@apache.org> on 2017/05/18 18:42:04 UTC
[jira] [Commented] (BEAM-39) Audit trigger implementations to
ensure they prefetch appropriately
[ https://issues.apache.org/jira/browse/BEAM-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016231#comment-16016231 ]
Daniel Halperin commented on BEAM-39:
-------------------------------------
[~scwhittle] Is this issue resolved? If not, are you working on this issue – or should it be unassigned?
cc [~kenn]
> Audit trigger implementations to ensure they prefetch appropriately
> -------------------------------------------------------------------
>
> Key: BEAM-39
> URL: https://issues.apache.org/jira/browse/BEAM-39
> Project: Beam
> Issue Type: Task
> Components: runner-core, sdk-java-core
> Reporter: Kenneth Knowles
> Assignee: Sam Whittle
> Labels: Triggers
>
> Each method of the implementation of a trigger as an onElement/onFire/shouldFire state machine has a corresponding method to register any state it intends to read, so that state can be read in a single batch per bundle.
> This task is to read them over ensuring prefetching is adequate, and potentially create a test harness to do this generically.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)