hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6894) Common foundation for Hadoop client tools
Date Mon, 02 Aug 2010 17:54:19 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894622#action_12894622

Owen O'Malley commented on HADOOP-6894:

  1. We desperately need a packaging and deployment strategy in Hadoop. The current tarballs
based deployment is  insufficient.
  2. A lot of discussion of potential layouts for deployment already happened on HADOOP-6255,
which you've completely ignored. Installing each tool is a separate directory with the tool
and version name is how it was done before we had package managers. Package managers have
taken over because they are far more convenient than tarballs with install instructions. I
don't think this proposal is moving the project in the correct direction. Granted, we probably
need to produce tarballs for operating systems without package managers, but certainly I'd
expect most installations to use packages.
  3. Any packaging and/or deployment strategy that ignores cluster deployment won't work.
  4. Naming versions based on the Hadoop version makes sense, but should only be to the branch.
(ie. pig-0.7-0.20 not pig-0.7-0.20.2). Naturally this Jira isn't the place to discuss changes
in other sub-projects (ie Pig).

> Common foundation for Hadoop client tools
> -----------------------------------------
>                 Key: HADOOP-6894
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6894
>             Project: Hadoop Common
>          Issue Type: New Feature
>            Reporter: Alejandro Abdelnur
>         Attachments: HadoopClientTools.pdf
> As Hadoop widespreads and matures the number of tools and utilities for users keeps growing.
> Some of them are bundled with Hadoop core, some with Hadoop contrib, some on their own,
some are full fledged servers on their own. For example, just to name a few: distcp, streaming,
pipes, har, pig, hive, oozie.
> Today there is no standard mechanism for making these tools available to users. Neither
there is a standard mechanism for these tools to integrate and distributed them with each
> The lack of a common foundation creates issues for developers and users.

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

View raw message