Mailing-List: contact avro-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: avro-dev@hadoop.apache.org
Message-ID: <502431323.1251495932886.JavaMail.jira@brutus>
Date: Fri, 28 Aug 2009 14:45:32 -0700 (PDT)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: avro-dev@hadoop.apache.org
Subject: [jira] Updated: (AVRO-108) add binary comparator
In-Reply-To: <2057634492.1251477512907.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Doug Cutting updated AVRO-108:
------------------------------

    Fix Version/s: 1.0.1
         Assignee: Doug Cutting
           Status: Patch Available  (was: Open)

This is all-new code and includes tests.  I'll commit it soon unless someone objects.

> add binary comparator
> ---------------------
>
>                 Key: AVRO-108
>                 URL: https://issues.apache.org/jira/browse/AVRO-108
>             Project: Avro
>          Issue Type: New Feature
>          Components: java
>            Reporter: Doug Cutting
>            Assignee: Doug Cutting
>             Fix For: 1.0.1
>
>         Attachments: AVRO-108.java
>
>
> Hadoop MapReduce performance benefits greatly if data may be compared without deserializing to an object, but rather by examining its serialized bytes directly.  Such "raw" comparators are typically written by hand in Hadoop, and are very fragile.
> With Avro it is possible to generically compare two serialized byte sequences if their schema is known.  This should work for any Avro data, regardless of how it was serialized or how it will be deserialized.

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