hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6894) Common foundation for Hadoop client tools
Date Tue, 03 Aug 2010 01:48:19 GMT

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

Alejandro Abdelnur commented on HADOOP-6894:

Thanks Owen,

I have not ignored HADOOP-6255, the proposal integrates some of the ideas discussed there
(there is still no consensus on some of them in HADOOP-6255):

* A common directory layout
* Support for native components
* TAR files as initial distro from where native packages are created

Regarding your other comments:

1. Yes, we need clear story for packaging.
2. Tarballs on its own are not sufficient. IMO tarballs with metadata that allows the creation
of native packages are. If you are using tarballs directly, you have to resolve dependencies
by hand, if you are using native packages things are done for you. A packager project can
use the tarballs+metadata to create native packages.
3. Cluster deployment is a complete different beast and that is why it is ignored by this
proposal, this proposal focuses on a solution for users (the client side of things).
4. This Jira only recommends (it does not impose) a consistent versioning for client tools
that would make things simpler for the users. 

> 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