hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1053) Make Record I/O functionally modular from the rest of Hadoop
Date Sun, 04 Mar 2007 21:07:50 GMT

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

Tom White commented on HADOOP-1053:

To answer Milind's question about modularity: I would favour modularity via separate jars.
It's what many other projects do (two examples: Apache ActiveMQ, Spring) so it is well understood
by users. A jar containing all of core Hadoop would be supplied too as a convenience (as it
is now).

The dependencies look something like this (assuming the ASCII art doesn't get too mangled):

^  ^ ^
|   |   |
fs | record
^  |
|   |

So, for example, users who only required HDFS would just need hadoop-common.jar and hadoop-fs.jar.

If desired, we could split the javadoc to reflect the modules using the grouping mechanism

(All this would be a separate Jira issue obviously.)

> Make Record I/O functionally modular from the rest of Hadoop
> ------------------------------------------------------------
>                 Key: HADOOP-1053
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1053
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: record
>    Affects Versions: 0.11.2
>         Environment: All
>            Reporter: Milind Bhandarkar
>         Assigned To: Milind Bhandarkar
>             Fix For: 0.13.0
>         Attachments: jute-patch.txt
> This issue has been created to separate one proposal originally included in HADOOP-941,
for which no consensus could be reached. For earlier discussion about the issue, please see
> I will summarize the proposal here.  We need to provide a way for some users who want
to use record I/O framework outside of Hadoop.

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

View raw message