hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Milind Bhandarkar (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-1053) Make Record I/O usable from independent of Hadoop
Date Fri, 02 Mar 2007 23:28:50 GMT

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

Milind Bhandarkar updated HADOOP-1053:

    Attachment: jute-patch.txt

Based on the discussion in HADOOP-948, thiss patch implements what I think should be an acceptable
compromise for now.

The generated code does not contain any references to classes/interfaces outside org.apache.hadoop.record.

Thee runtime dependency on threee classes/interfaces in org.apache.hadoop.io, i.e. WritableComparable,
WritableUtils, and WritaableComparator is moved into the runtime code in org.apache.hadoop.record.

This patch also fixes the wrong binary serialization of -ve longs and -ve ints (thanks David).

When rcc is invoked without any parameters, it now prints the correct usage (instead of just
saying "no input files specified."

Also provided is a fix to the package documentation.

> Make Record I/O usable from independent 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
>         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