[
https://issues.apache.org/jira/browse/SAMZA-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200848#comment-16200848
]
Prateek Maheshwari commented on SAMZA-1391:
-------------------------------------------
cc [~bharathkk] to confirm that SAMZA-1454 addresses this issue.
> System generated intermediate streams should have robust naming scheme
> ----------------------------------------------------------------------
>
> Key: SAMZA-1391
> URL: https://issues.apache.org/jira/browse/SAMZA-1391
> Project: Samza
> Issue Type: Bug
> Reporter: Bharath Kumarasubramanian
>
> In certain class of high level stream applications, Samza takes care of
> creating intermediate streams. Currently, we use the combination of job name,
> job id and the operator id to come up with the logical and physical stream
> name. We need to come up with a unique, robust naming scheme to prevent
> collision. We need to either use a unique name or detect the collision and
> perform necessary purge/cleanup steps prior to stream creation.
> An example where this bug is exploited is...
> Consider a stream application with following phases.
> {quote} input --> partition --> output {quote}
> If the input source were to change or the user provided partition function
> changes, our DAG would still be the same resulting in the same logical and
> physical stream name.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
