When looking at changing the way configuration works, it might be worth a glance at the Config API from the MicroProfile project[1]. Among other things, it attempts to abstract away where config data comes from, as well as supporting dynamic changes in some cases.
Craig McClanahan [1] http://microprofile.io/project/eclipse/microprofile-config On Thu, Dec 21, 2017 at 9:48 AM, Steve Blackmon <[email protected]> wrote: > Hi dev@streams, > > One of our project objectives that I feel strongly about and want to make > progress on in 2018 is to reduce disparities between the configuration > objects that initialize similar providers from various data sources. > > TL;DR - The way a provider is launched should be based on the category of > data expected and the constraints that are expected to hold on the > normalized version of that data. Not based on the internals of how the > provider goes about obtaining that data as is currently the case. > > I’ve created a wiki page to get into the design of this fairly significant > change, and would appreciate your feedback and participation in the > process. > > https://cwiki.apache.org/confluence/display/STREAMS/ > Common+Provider+Config+Format > > Thanks, > Steve >
