[
https://issues.apache.org/jira/browse/SAMZA-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15934964#comment-15934964
]
Prateek Maheshwari commented on SAMZA-1159:
-------------------------------------------
We're currently using the StreamSpec as a mapping b/w the logical streamId and
the system + physical stream name. Removing StreamSpec from
SamzaContainer/StreamGraph etc. requires Systems to be able to send and receive
messages with just the streamId (i.e. w/o needing the system and physical
stream name).
> Move StreamSpec from a public API to an ApplicationRunner internal API
> ----------------------------------------------------------------------
>
> Key: SAMZA-1159
> URL: https://issues.apache.org/jira/browse/SAMZA-1159
> Project: Samza
> Issue Type: Task
> Reporter: Prateek Maheshwari
> Assignee: Prateek Maheshwari
> Fix For: 0.13.0
>
>
> We can remove the creation and usage of StreamSpec from the public API for
> StreamApplication for now. Users will now be able to create an
> input/output/intermediate stream by specifying its ID. StreamSpec will be
> created by the ExecutionPlanner from config using the ApplicationRunner.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
