hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Loughran <ste...@hortonworks.com>
Subject Re: Putting the hdfs client as a separate jar
Date Thu, 03 Apr 2014 12:00:52 GMT
On 3 April 2014 00:02, Haohui Mai <hmai@hortonworks.com> wrote:

> The rpc and the web client can stay in one jar for the first cut. Indeed it
> might introduce some extra dependency, but the downstream projects always
> have the option to implement the webhdfs protocol themselves if they really
> need to avoid the dependency.
>
> Hadoop common is a bigger problem. Indeed the hadoop common jar needs to be
> separated into smaller modules to minimize the dependency. This needs to be
> addressed as well.
>

-1

its not needed, and having >1 JAR only introduces a new problem
"inconsistent versions of tightly coupled libraries on the classpath".

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

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