Mailing-List: contact gora-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: gora-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of enis.soz@gmail.com designates
 74.125.83.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGaRif1+wZb8TN3Q_WjGnHFqjU-eMB6cuhQbe-Bg3=A7Jr78Rw@mail.gmail.com>
References: 
 <CAGaRif1+wZb8TN3Q_WjGnHFqjU-eMB6cuhQbe-Bg3=A7Jr78Rw@mail.gmail.com>
From: =?UTF-8?Q?Enis_S=C3=B6ztutar?= <enis.soz@gmail.com>
Date: Mon, 23 Jan 2012 10:04:18 -0800
Message-ID: 
 <CAMUu0w-nw_NjLOCAKD6qA5u7x9OoExXBkLRwMPBBZ-485DKRsQ@mail.gmail.com>
Subject: Re: Difference between Avro SpecificCompiler & GoraCompiler
To: gora-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=0016364269553688c204b735dd21

--0016364269553688c204b735dd21
Content-Type: text/plain; charset=UTF-8

Hi,

GoraCompiler is the class which adds gora specific class methods and fields
to the compiled classes, so that they implement the Persistent interface,
etc. At the time of developing for the first version of Gora, the
SpecificCompiler class was not extendable and we did not want to deal with
patching Avro, so we just fetched the code for the Specific compiler, and
changed it, which I admit, is a huge hack. Now that Avro's specific
compiler seems to have changed to use Velocity, it might be more
extensible, but I doubt that, we can just extend it without needing to
change the code. So, I am +1 for updating the code for Avro, but the we
might need to update GoraCompiler as well.

Thanks,
Enis

On Sat, Jan 21, 2012 at 10:13 AM, Lewis John Mcgibbney <
lewis.mcgibbney@gmail.com> wrote:

> Hi Guys,
>
> Been messing around with the compiler today and got curious about some
> things.
>
> 1) As this thread states, what is the specific difference between our own
> compiler [1] implementation and the Avro SpecificCompiler [2] we have a
> choice of using via bin/gora specificcompiler?
> 2) I was going to suggest that we upgrade to Avro version 1.6.1 (most
> recently tagged stable), as the project seems to be more matured, there has
> also been some code refactoring going on.
> 3) I've attached a link [3] to the current SpecificCompiler class within
> the recent 1.6.1 release, even this class has increased in lines of code by
> around 50%, therefore I think there is more functionality to be had from
> upgrading.
>
> The reason I'm asking is that I've been working on GORA-27, however I
> wonder if it is better to work towards an implementation for Avro, and we
> could then rely on that implementation rather than writing one solely for
> Gora which can only be used here? This story, however falls through if
> there is a strong case for us maintaining our own compiler implementation.
>
> What do you guys think?
>
> [1]
>
> http://svn.apache.org/viewvc/incubator/gora/trunk/gora-core/src/main/java/org/apache/gora/compiler/GoraCompiler.java?view=markup
> [2]
>
> http://svn.apache.org/viewvc/avro/tags/release-1.3.3/lang/java/src/java/org/apache/avro/specific/SpecificCompiler.java?view=markup
> [3]
>
> http://svn.apache.org/viewvc/avro/tags/release-1.6.1/lang/java/compiler/src/main/java/org/apache/avro/compiler/specific/SpecificCompiler.java?view=markup
> --
> *Lewis*
>

--0016364269553688c204b735dd21--