[
https://issues.apache.org/jira/browse/SAMZA-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894585#comment-15894585
]
ASF GitHub Bot commented on SAMZA-1096:
---------------------------------------
GitHub user jmakes opened a pull request:
https://github.com/apache/samza/pull/74
SAMZA-1096: StreamSpec constructors in the ExecutionEnvironments
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jmakes/samza samza-1096
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/samza/pull/74.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #74
----
commit e05f1692cdc8aa0aa49d02a13114ef7aef39679a
Author: Jacob Maes <[email protected]>
Date: 2017-02-24T00:22:22Z
SAMZA-1096: StreamSpec constructors in the ExecutionEnvironments first
draft, needs more documentation work.
commit 730430f74283f42f2562224a086ba0e317ec72a1
Author: Jacob Maes <[email protected]>
Date: 2017-02-24T00:22:22Z
SAMZA-1096: StreamSpec constructors in the ExecutionEnvironments
Refinements and documentation.
commit cde41414dc640f39d9412942e68519c019664633
Author: Jacob Maes <[email protected]>
Date: 2017-03-03T15:41:39Z
Merge branch 'master' into samza-1096
----
> 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)
