hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-6381) WritableUtils::*VLong utilities should be available for byte arrays
Date Mon, 23 Nov 2009 00:39:39 GMT

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

Chris Douglas updated HADOOP-6381:

    Resolution: Won't Fix
        Status: Resolved  (was: Patch Available)

bq. I would also like to discourage the introduction of such ad-hoc apis in io.WritableUtil

One could respond that WritableUtil contains only ad-hoc APIs, that many patches are still
submitted without knowing best-practices for working with Writables (e.g. a patch recently
posted to HADOOP-6373 uses ByteArray\*Streams to read vints from byte[]), and the day when
Avro rescues Hadoop's users from byte-oriented interfaces is still in the future.

However, your point that what ails Writables can't be fixed with more utility functions is
irrefutable and undisputed. Adding them so late in Writable's life makes the "confused user"
argument even less compelling. I'll close this as "won't fix".

> WritableUtils::*VLong utilities should be available for byte arrays
> -------------------------------------------------------------------
>                 Key: HADOOP-6381
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6381
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: util
>            Reporter: Chris Douglas
>            Priority: Minor
>         Attachments: C6381-0.patch, C6381-1.patch, C6381-2.patch
> Particularly when working with raw bytes in Writables, it is often useful to have versions
of the vint utility functions for byte arrays.

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

View raw message