[SAMZA-1096] StreamSpec constructors in the ExecutionEnvironments

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.13.0
• Assignee: Jake Maes
• Reporter: Jake Maes
• Created: 21/Feb/17 17:29
• Updated: 06/Mar/17 22:53
• Resolved: 06/Mar/17 22:53

Description

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.

Issue Links

• links to: GitHub Pull Request #74