The following may be very specific an experience, but I felt you guys may benefit from it:
>From my experience, this confusion (where one would type /etc/hadoop/hdfs-site.xml quickly instead of /etc/hadoop/conf/hdfs-site.xml) has indeed come up a (very) few times with users/admins I've interacted with over the last year. These users had never used tarball setups before, and didn't know of the "conf" name and what that signifies. I _personally_ am comfortable with /etc/hadoop/conf naming and instructions cause I came to package-world after much tarball usage/deployments. I'm OK with the change in general if it happens (its "standard" to have files directly under /etc/app-name, and all apps ought to be consistent), but I humbly wish we would not change for any existing major releases. That'd cause much user pain for those already gotten used to this (and *many* have). It would also break quite a few puppet/chef scripts I think. On Tue, May 1, 2012 at 10:58 AM, Owen O'Malley <[email protected]> wrote: > I'd like to propose that we change the default value for > HADOOP_CONF_DIR to /etc/hadoop instead of the current > /etc/hadoop/conf. I think it will reduce the confusion factor of new > users quite a bit. Roman shared that the original motivation was to > support multiple client configurations, but that seems relatively rare > use case. (Note that multiple client configs is still supported, of > course, you just need to use --config option to point it to the right > configuration directory. I'm just proposing that we remove the extra > conf out of the path.) > > What do people think? > > -- Owen -- Harsh J
