[ 
https://issues.apache.org/jira/browse/BIGTOP-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225793#comment-13225793
 ] 

Roman Shaposhnik commented on BIGTOP-423:
-----------------------------------------

Here's the current proposal (which is a bit less ambitious than the original 
intent since hadoop is still not fully ready to be cleanly split into 
server/client parts at the level of jar files):
   # we are going to have an extra package called hadoop-client
   # hadoop-client will depend on hadoop, hadoop-hdfs, hadoop-yarn and 
hadoop-mapreduce since they all have client and server bits co-mingled in their 
respective jar files
   # hadoop-client package will install a bunch of the symbolic links under 
/usr/lib/hadoop/lib/client pointing to all the jar files in the packages it 
depends upon 

That way we will have a single location to be added to the client's class path 
(/usr/lib/hadoop/lib/client) and we can slowly work on spliting the actual jar 
files between the client and server packages.

Thoughts?
                
> hadoop package needs to be split into hadoop-client and hadoop-server packages
> ------------------------------------------------------------------------------
>
>                 Key: BIGTOP-423
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-423
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>            Priority: Blocker
>             Fix For: 0.4.0
>
>
> Currently hadoop package co-bundles together dependencies for the daemons of 
> hadoop (HDFS, YARN) and client side of the same projects. It would be much 
> nicer to split this functionality into 2 separate packages so that downstream 
> components (Pig,Hive,Oozie) don't have to depend on more bits than they have 
> to.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to