Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1766969132.1221523064402.JavaMail.jira@brutus>
Date: Mon, 15 Sep 2008 16:57:44 -0700 (PDT)
From: "Owen O'Malley (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-4151) Add a memcmp-compatible interface for
 key types
In-Reply-To: <1145072740.1221083324339.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Owen O'Malley updated HADOOP-4151:
----------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]  (was: [Incompatible change])
          Status: Resolved  (was: Patch Available)

I just committed this. Thanks, Chris!

> Add a memcmp-compatible interface for key types
> -----------------------------------------------
>
>                 Key: HADOOP-4151
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4151
>             Project: Hadoop Core
>          Issue Type: Improvement
>            Reporter: Chris Douglas
>            Assignee: Chris Douglas
>            Priority: Minor
>             Fix For: 0.19.0
>
>         Attachments: 4151-0.patch, 4151-1.patch, 4151-2.patch, 4151-3.patch, 4151-4.patch
>
>
> Sometimes it's beneficial to treat types (like BytesWritable and Text) as byte arrays, agnostic to their type. Adding an interface to tag key types as amenable to this treatment can permit optimizations and reuse for that subset of types in tools and libraries.

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