You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@streams.apache.org by "Steve Blackmon (JIRA)" <ji...@apache.org> on 2017/09/13 01:15:00 UTC

[jira] [Resolved] (STREAMS-527) Move default values on configuration beans from json schemas into typesafe reference.conf files

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

Steve Blackmon resolved STREAMS-527.
------------------------------------
    Resolution: Fixed

> Move default values on configuration beans from json schemas into typesafe reference.conf files
> -----------------------------------------------------------------------------------------------
>
>                 Key: STREAMS-527
>                 URL: https://issues.apache.org/jira/browse/STREAMS-527
>             Project: Streams
>          Issue Type: Task
>            Reporter: Steve Blackmon
>            Assignee: Steve Blackmon
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> A problem is introduced when merging configuration objects when the default values are initialized on object creation.  Specifically, it becomes much harder to create partial configurations to merge, as every instance of the configuration class contains the default values across most fields.
> Typesafe config provides a recommended method for managing default values by putting a reference.conf in each module containing defaults.
> Going this route, creating a streams configuration bean with StreamsConfigurator or a component configuration bean with ComponentConfigurator will work exactly as before, and create a bean with a constructor will contain only the fields that are explicitly set by user code, ensuring that merging an ordered list of beans with juneau PojoMerge or similar methods will do exactly what is asked instead of messing up on fields with defined defaults.



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