hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Wang <andrew.w...@cloudera.com>
Subject Re: [DISCUSS] Changing the default class path for clients
Date Mon, 03 Apr 2017 17:26:26 GMT
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.


On Mon, Apr 3, 2017 at 9:04 AM, Allen Wittenauer <aw@effectivemachines.com>

>         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-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-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org

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