drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Chen <tnac...@gmail.com>
Subject Re: next steps
Date Thu, 11 Oct 2012 18:56:16 GMT
Hi,

I don't think there is any design documents, except one overall
architecture slides online (available on the drill website).

There is a grammer definition and early parser prototype done in the
https://github.com/ApacheDrill/parser repo.

Tim

On Thu, Oct 11, 2012 at 11:37 AM, arunabh ghosh <aru_nabh@yahoo.com> wrote:

> Hi Folks,
>                   I've been a silent reader on this group for a while. It
> looks like some concrete work items are beginning to form and I was
> wondering how folks can start getting involved. I would be very interested
> in helping out with the parser. Are there any design documents/early source
> that we can look at ?
>
>
>
>
> ________________________________
>  From: Ted Dunning <ted.dunning@gmail.com>
> To: drill-dev@incubator.apache.org
> Sent: Thursday, October 11, 2012 12:59 AM
> Subject: next steps
>
> I would like to shepherd the web front end, the query parser and some
> documentation into the project next.
>
> Michael,
>
> You have the web front end ready it sounds like.  Can you provide us a
> walk-through?
>
> Camuel,
>
> You and your team have the parser in some kind of shape.  We still need to
> discuss and settle on an intermediate language to pass to the query
> optimizer and source code organization.  Also, how does the syntax below
> look to you as a target?
>
> Julian H,
>
> Can you comment on what you would like to see as a logical plan syntax?  My
> thought was to describe the logical plan as virtual assignments in a style
> similar to (but very distinct from) LLVM.  The syntax would look something
> like this:
>
>    dest := op arg1, arg2, ... argN
>
> op would be one of a small list of operators.  Arg's would be destinations
> from earlier in the file.  Even arithmetic expressions and built-in
> functions would be in this form.
>
> Would this look OK to you?
>
> If so, what list of op's should we target first?
>

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