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 2018/01/12 19:27:05 UTC

[jira] [Updated] (SAMZA-1244) StreamConfig should validate samza.* configs

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

Jake Maes updated SAMZA-1244:
-----------------------------
    Fix Version/s:     (was: 0.14.0)
                   0.15.0

> StreamConfig should validate samza.* configs
> --------------------------------------------
>
>                 Key: SAMZA-1244
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1244
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Jake Maes
>            Assignee: Jake Maes
>             Fix For: 0.15.0
>
>
> We had  a scenario where a user specified the following property:
> streams.myStreamId.samza.physical.stream=myPhysicalName
> when the actual property should have been 
> streams.myStreamId.samza.physical.name=myPhysicalName
> For general stream properties, we can't know if they are correct. But everything after the ".samza." scope can be validated against the known samza stream configs and a warning could be thrown if it's not valid.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)