[
https://issues.apache.org/jira/browse/HADOOP-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666267#action_12666267
]
Doug Cutting commented on HADOOP-4868:
--------------------------------------
> Do you mean build dependencies?
I think Owen's plan is to use Ivy for build-time dependencies on hadoop-core,
but not to bundle the core jar into releases like other jars we get from Ivy,
rather to force folks to explicitly install a compatible version of core. The
idea is to make it easier for folks to separately upgrade hdfs, core and mapred.
However will we run into library conflicts? It would be bad if core and hdfs
bundle different versions of dependent jars. So I wonder if we should use Ivy
at install time to get a single version of dependent libraries, or whether we
should just be very careful not to, e.g., bundle libraries in hdfs that are
also bundled in core. If we used Ivy for other libraries at install-time, that
begs the question whether we should also use it to get core at install time.
If we did this, then one would configure Ivy in order to upgrade to a newer
version of core. But Owen's goal is to make Hadoop play well with Linux
package managers, which probably means not using Ivy at install time.
> Split the hadoop script into 3 parts
> ------------------------------------
>
> Key: HADOOP-4868
> URL: https://issues.apache.org/jira/browse/HADOOP-4868
> Project: Hadoop Core
> Issue Type: Improvement
> Components: scripts
> Reporter: Sharad Agarwal
> Assignee: Sharad Agarwal
> Attachments: 4868_v1.patch, 4868_v2.patch
>
>
> We need to split the bin/hadoop into 3 parts for core, mapred and hdfs. This
> will enable us to distribute the individual scripts with each component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
