drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacques Nadeau <jacques.dr...@gmail.com>
Subject Re: report of off-line conversations and develpments
Date Thu, 10 Jan 2013 21:30:53 GMT
Hey Andrew

I hope the holidays treated you well.

I think you have fair concerns.  Quite a bit of the initial discussions
have happened in the generally accessible Drill Syntax google doc.  That
being said, more needs to happen on JIRA and source control.  I'm currently
working on Drill-5 and was hoping that I could send/share something shortly
that people can respond to.  Because the purpose of the Reference
Interpreter is somewhat ephemeral, I've been more focused on getting
something out that is good enough which is why less discussion has happened
in JIRA.  Part of this was for expedience and part due to me gaining my
bearings on the Apache Drill vision.

Glad you're interested and engaged in this as I think having you work on
some of these pieces would be huge for the Drill community.

I will work to get something up shortly.

Thanks again,

On Thu, Jan 10, 2013 at 11:29 AM, Andrew Purtell <apurtell@apache.org>wrote:

> I'm really curious why none of this is on the Drill JIRA or in it's version
> control.
> On Thu, Jan 10, 2013 at 10:59 AM, Ted Dunning <ted.dunning@gmail.com>
> wrote:
> > - There have been several proposals for syntax conventions for the
> logical
> > plan language.  Three versions have been built.  I built a version along
> > the lines of LLVM and a JSON based version that used a constructor
> > convention along with tight binding of classes to operator types.
>  Jacques
> > built a version on Jackson which used much looser binding and supported
> > structuring much more easily.  Overall, I feel that Jacques
> implementation
> > dominates the ones that I have done in essentially every way.  I think we
> > should go with his style.
> >
> --
> Best regards,
>    - Andy
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message