You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Yan Fang (JIRA)" <ji...@apache.org> on 2015/04/17 20:41:59 UTC

[jira] [Commented] (SAMZA-655) Add environment variable configuration rewriter.

    [ https://issues.apache.org/jira/browse/SAMZA-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500404#comment-14500404 ] 

Yan Fang commented on SAMZA-655:
--------------------------------

Thank you, Dan. What kind of use case does this function apply? IMHO, feel if the user wants to change some configs, they can always do that in the config file.

> Add environment variable configuration rewriter.
> ------------------------------------------------
>
>                 Key: SAMZA-655
>                 URL: https://issues.apache.org/jira/browse/SAMZA-655
>             Project: Samza
>          Issue Type: New Feature
>            Reporter: Dan Harvey
>            Assignee: Dan Harvey
>            Priority: Minor
>         Attachments: 0001-SAMZA-655-Add-EnvironmentConfigRewriter-to-samza-api.patch
>
>
> It is useful to be able to change configuration via system environment variables. It makes sense to do this in Samza via a ConfigRewriter.
> The proposed spec is as follows.
>  - Take all env variables that start with SAMZA_ and strip this prefix.
>  - Downcase the renaming key
>  - Convert underscores to fullstop
> So you will have SAMZA_FOO_BAR -> foo.bar as a samza config key.
> This means environment variable keys will conform to usual standards. The downside to this is that property keys in samza would not be able to have uppercase characters or _ as they would be ambiguous when mapping names.
> Still even with these limitations I think it is useful.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)