You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Prateek Maheshwari (JIRA)" <ji...@apache.org> on 2017/04/17 03:37:41 UTC

[jira] [Updated] (SAMZA-1075) Refactor SystemAdmin Interface to expose a common method to create streams.

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

Prateek Maheshwari updated SAMZA-1075:
--------------------------------------
    Fix Version/s: 0.13.0

> Refactor SystemAdmin Interface to expose a common method to create streams.
> ---------------------------------------------------------------------------
>
>                 Key: SAMZA-1075
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1075
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Jake Maes
>            Assignee: Jake Maes
>             Fix For: 0.13.0
>
>
> With samza-1041, we plan to automatically create intermediate streams for a given graph. To do this, we need a generic way to create streams on all supported systems. 
> We currently auto-create streams for checkpoints, coordinatorStream, and changelogs, we do so using a fragmented set of interfaces and methods. e.g. to create a checkpoint topic, the KafkaCheckpointMnager.start() creates the topic using KafkaUtil directly, whereas for the coordinatorStream, we call the SystemAdmin.createCoordinatorStream() method. The former is specific to a particular System, but the latter is theoretically (but not actually) implemented for every System. 
> Instead of using custom methods in differing levels of abstraction, we should just expose one simple createStream() method in the SystemAdmin interface and deprecate the old methods. The new createStream method will receive a complete, system-specific blueprint/specification for the stream and use that to create the actual stream. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)