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/04/05 14:03:00 UTC
[jira] [Updated] (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 updated BEAM-4016:
-------------------------------
Attachment: sdf-splitrestriction-lifeycle-test.patch
> 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
> Reporter: Ismaël Mejía
> Assignee: Thomas Groh
> Priority: Major
> Attachments: sdf-splitrestriction-lifeycle-test.patch
>
>
> SplitRestriction is the method where we can split in advance 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)