apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sandeep Deshmukh <sand...@datatorrent.com>
Subject Re: Precedence of configuration settings
Date Thu, 19 Nov 2015 14:50:30 GMT
Ram: Could you please explain a bit more. Not sure if I have understood
your question.

If you have custom.xml in the conf directory, dtcli will not pick it up.

dtcli will pick  conf/dt-site.xml followed by .dt/dt-site.xml files, no
other files are loaded. If the user wants to use custom.xml, he/she needs
to explicitly pass it with -conf option while launching the application and
that will override  conf/dt-site.xml and .dt/dt-site.xml.


On Thu, Nov 19, 2015 at 4:27 AM, Munagala Ramanath <ram@datatorrent.com>

> Application properties can currently appear in multiple places; the
> precedence of these
> occurrences is documented in the section entitled "Properties source
> precedence"
> at:
> https://docs.datatorrent.com/application_packages/
> Consider a scenario where a property is specified in 3 places:
> 1. ~/.dt/dt-site.xml as A
> 2. In the properties.xml file of the application as B
> 3. In a custom property file in site/conf/custom.xml which is just a
> copy of properties.xml (also B).
> Launching the application normally uses A
> Launching with custom.xml uses B even though this file is identical to
> properties.xml.
> This can be confusing for someone who simply copies over
> properties.xml to a new custom
> file, changes a value and uses the file at launch time, only to
> discover that settings
> that he/she DID NOT change have mysteriously been affected.
> Having custom properties files behave exactly the same as
> properties.xml in the application
> seems more natural: either both should override settings in
> dt-site.xml or neither should.
> What do people think ?
> Ram

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message