You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Ismaël Mejía (JIRA)" <ji...@apache.org> on 2018/07/06 21:23:00 UTC

[jira] [Assigned] (BEAM-4016) Direct runner incorrect lifecycle, @SplitRestriction should execute after @Setup on SplittableDoFn

     [ https://issues.apache.org/jira/browse/BEAM-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ismaël Mejía reassigned BEAM-4016:
----------------------------------

    Assignee: Ismaël Mejía

> Direct runner incorrect lifecycle, @SplitRestriction should execute after @Setup on SplittableDoFn
> --------------------------------------------------------------------------------------------------
>
>                 Key: BEAM-4016
>                 URL: https://issues.apache.org/jira/browse/BEAM-4016
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-direct
>    Affects Versions: 2.4.0, 2.5.0
>            Reporter: Ismaël Mejía
>            Assignee: Ismaël Mejía
>            Priority: Major
>         Attachments: sdf-splitrestriction-lifeycle-test.patch
>
>
> The method annotated with @SplitRestriction is the method where we can define the RestrictionTrackers (splits) in advance in a SDF. It makes sense to execute this after the @Setup method given that usually connections are established at Setup and can be used to ask the different data stores about the partitioning strategy. I added a test for this in the SplittableDoFnTest.SDFWithLifecycle test.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)