Mailing-List: contact avro-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: avro-user@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of eelco.hillenius@gmail.com
 designates 209.85.211.177 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=vdwYafC/KBQepu41srh9mB4q6zdQl2HpskbZr0r5gvhy3H6yxi7w6ZFf6DqmAEw1E7
         TFHHFJ4KxPBWwf4Wk0IYoLNkJehIPD77wArEHwmAKiq8BuxoJ9BUioqTJMhRz/t/1OoN
         25yOzUiEuFIltl1WAtMt4phs0LT03khmZQcps=
MIME-Version: 1.0
In-Reply-To: <4A9EA5EA.5020306@apache.org>
References: <C6C3E302.1049A%scott@richrelevance.com>
 <4A9EA5EA.5020306@apache.org>
From: Eelco Hillenius <eelco.hillenius@gmail.com>
Date: Wed, 2 Sep 2009 10:30:06 -0700
Message-ID: <ceb609d80909021030n3eacd46eu9f81c0e296fb7172@mail.gmail.com>
Subject: Re: user experience
To: avro-user@hadoop.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

> I've found that generating classes with the specific API is both simpler =
and
> faster. =A0In particular, if you have a set of related classes, use a
> method-free protocol file (.avpr) to define them. =A0The Java classes are
> generated by an Ant task.

The reason we don't want to go for the specific API is because we like
our development process to be as minimal as possible, and that
includes avoiding code generation where we can. We're with fine paying
a performance penalty for that, especially since for our purposes Avro
with reflection is definitively fast (and compact) enough. And the
nice thing about Avro is that if certain records turn out to be
bottlenecks, we can always turn them into specific ones.

My 2c,

Eelco