Mailing-List: contact user-help@avro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@avro.apache.org
MIME-Version: 1.0
References: <9D090DE1-137E-43C6-81E3-D733C5D1FD46@rat.io>
In-Reply-To: <9D090DE1-137E-43C6-81E3-D733C5D1FD46@rat.io>
From: Evan McClain <aeroevan@gmail.com>
Date: Sun, 31 Jan 2016 00:13:37 +0000
Message-ID: 
 <CAOyqiMv4s8fukB420=12WvUaLBQjPS7DDp1vSH0d8TYBxP+UJQ@mail.gmail.com>
Subject: Re: Autogenerating Java classes from IDL
To: user@avro.apache.org
Content-Type: multipart/alternative; boundary=001a113eb888746e8b052a96241a

--001a113eb888746e8b052a96241a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I have used IDLs with the avro-maven-plugin and that worked for me.

Evan

On Sat, Jan 30, 2016, 8:52 AM tl <tl@rat.io> wrote:

> Hi,
>
> I started working with Avro only recently so maybe I missed something but
> it seems to me that schemas can be defined in JSON as well as in IDL but
> only from JSON schemas can builder classes be autogenerated. This is a pi=
ty
> since IDLs are much easier to write and read than the JSON representation=
.
> I wrote a few IDL schemas, converted them to avpr and tweaked those avpr
> files to become valid avsc schema files from which I autogenerated the
> classes. This is a rather convoluted process. I wouldn=E2=80=99t mind so =
much if I
> wouldn=E2=80=99t know that I or somebody else will have to update the sch=
emas and
> classes from time to time. This doesn=E2=80=99t look like a robust workfl=
ow.
>
> Deleting the IDLs and avpr files and doing updates only in the avsc
> schemas reduces the workflow to 2 steps but I loose the nice properties o=
f
> IDLs [0].
> Using only generic mapping would reduce the workflow by one step too but
> I=E2=80=99d loose static type checking.
>
> I=E2=80=99d love to be able to autogenerate the Java classes from the IDL=
s
> directly. Is there a way?
>
> Regards,
> Thomas
>
>
> [0] Regarding IDLs it would be cool if I could forward reference objects
> in the schema or even write nested schemas but that=E2=80=99s a relativel=
y minor
> gripe.
>
>
>

--001a113eb888746e8b052a96241a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I have used IDLs with the avro-maven-plugin and that worke=
d for me.</div><span>
</span><p dir=3D"ltr">Evan<br>
</p><span>
</span><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Sat, Jan 30, 2016=
, 8:52 AM=C2=A0tl &lt;<a href=3D"mailto:tl@rat.io">tl@rat.io</a>&gt; wrote:=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I started working with Avro only recently so maybe I missed something but i=
t seems to me that schemas can be defined in JSON as well as in IDL but onl=
y from JSON schemas can builder classes be autogenerated. This is a pity si=
nce IDLs are much easier to write and read than the JSON representation.<br=
>
I wrote a few IDL schemas, converted them to avpr and tweaked those avpr fi=
les to become valid avsc schema files from which I autogenerated the classe=
s. This is a rather convoluted process. I wouldn=E2=80=99t mind so much if =
I wouldn=E2=80=99t know that I or somebody else will have to update the sch=
emas and classes from time to time. This doesn=E2=80=99t look like a robust=
 workflow.<br>
<br>
Deleting the IDLs and avpr files and doing updates only in the avsc schemas=
 reduces the workflow to 2 steps but I loose the nice properties of IDLs [0=
].<br>
Using only generic mapping would reduce the workflow by one step too but I=
=E2=80=99d loose static type checking.<br>
<br>
I=E2=80=99d love to be able to autogenerate the Java classes from the IDLs =
directly. Is there a way?<br>
<br>
Regards,<br>
Thomas<br>
<br>
<br>
[0] Regarding IDLs it would be cool if I could forward reference objects in=
 the schema or even write nested schemas but that=E2=80=99s a relatively mi=
nor gripe.<br>
<br>
<br>
</blockquote></div>

--001a113eb888746e8b052a96241a--