I agreed with Andrew too. Users have relied for years on `hadoop classpath` for their script to launch jobs or other tools, perhaps no the best idea to change the behavior without providing a proper deprecation path.
thanks! esteban. -- Cloudera, Inc. On Mon, Apr 3, 2017 at 10:26 AM, Andrew Wang <andrew.w...@cloudera.com> wrote: > What's the current contract for `hadoop classpath`? Would it be safer to > introduce `hadoop userclasspath` or similar for this behavior? > > I'm betting that changing `hadoop classpath` will lead to some breakages, > so I'd prefer to make this new behavior opt-in. > > Best, > Andrew > > On Mon, Apr 3, 2017 at 9:04 AM, Allen Wittenauer <a...@effectivemachines.com > > > wrote: > > > > > This morning I had a bit of a shower thought: > > > > With the new shaded hadoop client in 3.0, is there any reason the > > default classpath should remain the full blown jar list? e.g., shouldn’t > > ‘hadoop classpath’ just return configuration, user supplied bits (e.g., > > HADOOP_USER_CLASSPATH, etc), HADOOP_OPTIONAL_TOOLS, and > > hadoop-client-runtime? We’d obviously have to add some plumbing for > daemons > > and the capability for the user to get the full list, but that should be > > trivial. > > > > Thoughts? > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > > For additional commands, e-mail: common-dev-h...@hadoop.apache.org > > > > >
