Hi thanks for that, much appreciated.
I guess they are in the jar files then ;O) I was really surprised to see
the default configs pulled in, especially considering I thought I was in
full control, I did a file search on an installation and saw the files and
jumped to the wrong conclusion.
I
Hi All,
I have just realised that my implementation of hadoop-2.4.1 is pulling in
all the default.xml files.
I have three copies of each in different directories, obviously at least
one of those is on the class path.
Anyway with all the effort to set up a site, it seems strange to me that I
I recommend against deleting or moving *-default.xml, because these files
may be supplying reasonable default values for configuration properties
that you haven't set in *-site.xml. We also put defaults into the code
itself in case a configuration property is found to be completely missing,
but
Aren't the *-default.xml files supposed to be inside the jars rather than
loose files?
Cheers
Chris Mawata
On Jul 21, 2014 12:59 PM, Chris Nauroth cnaur...@hortonworks.com wrote:
I recommend against deleting or moving *-default.xml, because these files
may be supplying reasonable default values
That's a good point. I'm not sure how bare *-default.xml files would be
showing up on a deployment outside the jars.
Chris Nauroth
Hortonworks
http://hortonworks.com/
On Mon, Jul 21, 2014 at 11:12 AM, Chris Mawata chris.maw...@gmail.com
wrote:
Aren't the *-default.xml files supposed to be
I suspect someone wanted to read through them to know tge defaults.
Chris
On Jul 21, 2014 2:16 PM, Chris Nauroth cnaur...@hortonworks.com wrote:
That's a good point. I'm not sure how bare *-default.xml files would be
showing up on a deployment outside the jars.
Chris Nauroth
Hortonworks
