[jira] [Updated] (SAMZA-1320) Changelog topic configuration should accept streams. configurations

["Jake Maes (JIRA)" <ji...@apache.org>]

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

Jake Maes updated SAMZA-1320:
-----------------------------
    Description: 
This is a follow up to SAMZA-1317, which solved the migration issue but doesn't allow users to use streams.<streamId>.* to set properties on the changelog. 

After this ticket, users will configure the changelog on a store as a streamId, like this:

{code}
streams.my-changelog-topic.samza.system = my-system
streams.my-changelog-topic.samza.physical.name = my.changelog.topic.name
streams.my-changelog-topic.some-system-specific-property = some-system-specific-value
stores.my-store.changelog = my-changelog-topic
{code}

We should resolve the provided system.topic configuration value against the new streams.<streamId> based configurations.


  was:
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.



> Changelog topic configuration should accept streams.<streamId> configurations
> -----------------------------------------------------------------------------
>
>                 Key: SAMZA-1320
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1320
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Jake Maes
>            Assignee: Jake Maes
>             Fix For: 0.13.0
>
>
> This is a follow up to SAMZA-1317, which solved the migration issue but doesn't allow users to use streams.<streamId>.* to set properties on the changelog. 
> After this ticket, users will configure the changelog on a store as a streamId, like this:
> {code}
> streams.my-changelog-topic.samza.system = my-system
> streams.my-changelog-topic.samza.physical.name = my.changelog.topic.name
> streams.my-changelog-topic.some-system-specific-property = some-system-specific-value
> stores.my-store.changelog = my-changelog-topic
> {code}
> 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)