[
https://issues.apache.org/jira/browse/HADOOP-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524892
]
Doug Cutting commented on HADOOP-1815:
--------------------------------------
> Is it required that all tools be released at the same frequency as the core
> hadoop system?
Pragmatically, yes. We don't want to call separate release votes for each
tool. Bundling tools with the core simplifies compatibility: otherwise each
tool would need to separately document which version of the core it is
compatible with. Etc.
I'm still on the fence about whether we need separate jars for each logical
tool, or whether we should just move all non-kernel code into a single
hadoop-tool.jar. In the case of Nutch, having all those plugins separate makes
builds go slower, and makes browsing the sources more awkward.
> 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.
