You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Jake Maes (JIRA)" <ji...@apache.org> on 2017/06/02 21:55:04 UTC

[jira] [Resolved] (SAMZA-1317) Changelog topic configuration should accept streams. configurations

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

Jake Maes resolved SAMZA-1317.
------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 0.14.0)
                   0.13.0

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

> Changelog topic configuration should accept streams.<streamId> configurations
> -----------------------------------------------------------------------------
>
>                 Key: SAMZA-1317
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1317
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Prateek Maheshwari
>            Assignee: Jake Maes
>             Fix For: 0.13.0
>
>
> Changelog topic configuration currently doesn't not work if we try to use a streams.streamId based configuration for the topic name. E.g.,
> {code}
> streams.my-changelog-topic.samza.system = my-system
> streams.my-changelog-topic.samza.physical.name = my.changelog.topic.name
> stores.my-store.changelog = my-changelog-topic
> {code}
> Expected changelog topic name = my.changelog.topic.name
> Actual changelog topic name = my-changelog-topic
> We should resolve the provided system.topic configuration value against the new streams.<streamId> based configurations.



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