hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Milind Bhandarkar (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1815) Separate client and server jars
Date Tue, 04 Sep 2007 04:04:58 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524609
] 

Milind Bhandarkar commented on HADOOP-1815:
-------------------------------------------

Just want to know other users' opinions.

Would it be a good idea for building a hadoop ecosystem, to separate all these client codes
into separate projects?

(one project - one artifact is a good thing (tm). Doug agrees on this, based on his previous
comments. For growing hadoop ecosystem, we need several artifacts, that can evolve separately,
and faster.)

For example, how about separating distcp as a hadoop-dependent, but separate project to provide
a high-bandwidth distributed copy ?

How about separating streaming into a separate projects as a mechanism for using time-tested
ways (aka stdin, and stdout) for passing data between plugins and hadoop ?


> Separate client and server jars
> -------------------------------
>
>                 Key: HADOOP-1815
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1815
>             Project: Hadoop
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.14.0
>         Environment: All
>            Reporter: Milind Bhandarkar
>             Fix For: 0.15.0
>
>
> For the ease of deployment, one should not have to change the server jars, and restart
clusters, when minor features on the client side are changed. This requireds separating client
and server jars for hadoop. Version numbers appended to hadoop jars can reflect the compatibility.
e.g. the server jar could be at 0.13.1, and the client jar could be at 0.13.2. In short, we
can treat the part following 0. as the "major" version number for now.
> This allows major client frameworks such as streaming and Pig happy. To my knowledge,
Pig uses hadoop's default jobclient. Whereas streaming uses its own jobclient. I would love
to change streaming to use the default hadoop jobclient, if I can make modifications to it
(e.g. to print more stats that are available from TaskReport, for example), if I do not have
to deploy the new version of the whole jar to the backend and restart the mapreduce cluster.
> (I thought there was already a bug filed for separating the client and server jar, but
I could not find it. Hence the new Jira. Sorry about duplication, if any.)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message