[jira] [Resolved] (SAMZA-1096) StreamSpec constructors in the ExecutionEnvironments

["Jake Maes (JIRA)" <ji...@apache.org>]

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

Jake Maes resolved SAMZA-1096.
------------------------------
    Resolution: Fixed

Issue resolved by pull request 74
[https://github.com/apache/samza/pull/74]

> StreamSpec constructors in the ExecutionEnvironments
> ----------------------------------------------------
>
>                 Key: SAMZA-1096
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1096
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Jake Maes
>            Assignee: Jake Maes
>             Fix For: 0.13.0
>
>
> SAMZA-1075 added the notion of a StreamSpec for describing streams to be created, validated, or simply used in a samza application.
> SAMZA-1073 added the basic Fluent API but directly instantiated StreamSpecs, which puts undue burden on the user. 
> This task is to provide a basic constructor(s) in the ExecutionEnvironments to enable users to easily create a StreamSpec.
> Goals:
> 1. ExecutionEnvironment can influence the type of StreamSpec returned. For example a TestExecutionEnvironment might return a StreamSpec corresponding to an in-memory Collection stream, whereas the production ExecutionEnvironments would return a more scalable option, such as a Kafka StreamSpec.
> 2. We want 1 constructor which derives everything (type, properties, system, etc) from config. 
> 3. We want to be able to add convenience constructors for various types, like streamFromFile() for a file impl. These can be added later, but the foundational work should support it.



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