You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gobblin.apache.org by "Hung Tran (JIRA)" <ji...@apache.org> on 2017/09/14 19:55:00 UTC

[jira] [Resolved] (GOBBLIN-236) Add a ControlMessage injector as a RecordStreamProcessor

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

Hung Tran resolved GOBBLIN-236.
-------------------------------
    Resolution: Fixed

Issue resolved by pull request #2090
[https://github.com/apache/incubator-gobblin/pull/2090]

> Add a ControlMessage injector as a RecordStreamProcessor
> --------------------------------------------------------
>
>                 Key: GOBBLIN-236
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-236
>             Project: Apache Gobblin
>          Issue Type: Task
>            Reporter: Hung Tran
>            Assignee: Hung Tran
>
> Add a ControlMessage injector as a RecordStreamProcessor.
> A ControlMessageInjector inspects an incoming record and can inject ControlMessages based on the content of the incoming record.
> One use case for this is the injection of MetadataUpdateControlMessages when the latest schema has been updated to trigger the update of the schema used by other constructs downstream from the ControlMessageInjector.
> Long running jobs are more likely to encounter issues due to the schema being updated after the start of the job.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)