avro generated vs. hadoop primitive types

[Aleksey Maslov <Al...@Lab49.com>]

Hi,

when I have in avro IDL file declaration of property:
array  vector;

the Java code generated is:
List vector;

why it is not typed as List?
I thought to communicate + de/serialize data-types – one must use Hadoop
defined types?

Thank you,
Aleksey


--
View this message in context: http://apache-avro.679487.n3.nabble.com/avro-generated-vs-hadoop-primitive-types-tp2676672p2676672.html
Sent from the Avro - Users mailing list archive at Nabble.com.

Re: avro generated vs. hadoop primitive types

[Harsh J <qw...@gmail.com>]

Hello,

On Mon, Mar 14, 2011 at 10:41 PM, Aleksey Maslov
<Al...@lab49.com> wrote:
> Hi,
>
> when I have in avro IDL file declaration of property:
> array  vector;
>
> the Java code generated is:
> List vector;
>
> why it is not typed as List?

Do you mean why it _is_ typed as a List? Am confused a little after
reading your question.

> I thought to communicate + de/serialize data-types – one must use Hadoop
> defined types?

Do you mean ArrayWritables here? Avro has its own ser/de-parts
(encoders/decoders), and does not make use of Hadoop Writables. Avro
is mainly a data serialization system in itself.

Avro can efficiently serialize/deserialize primitives and many
supported constructs. See
http://avro.apache.org/docs/current/spec.html for some details on the
hows/whats of Avro's serialization/deserialization :)

-- 
Harsh J
http://harshj.com