drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Dunning <ted.dunn...@gmail.com>
Subject Re: next steps
Date Mon, 15 Oct 2012 13:18:50 GMT
You can also fork the mirror on github and post a message on the JIRA to
that effect.  The patches are nice because they make the change visible
forever.  The github approach is nice because it effectively gives a code
review tool with no tooling.

On Mon, Oct 15, 2012 at 6:02 AM, Ted Dunning <ted.dunning@gmail.com> wrote:

> This is in place.  You can attach diffs in git format-patch format to
> relevant JIRA's
>
>
> On Mon, Oct 15, 2012 at 12:11 AM, Michael Hausenblas <
> michael.hausenblas@gmail.com> wrote:
>
>>
>> > So it sounds like I should create a sandbox area for components that we
>> > haven't integrated yet.
>> >
>> > Then I (or other committers) can commit to this area and as the
>> components
>> > come together, we can promote the best of each alternative to the real
>> deal.
>>
>> +1
>>
>> Cheers,
>>            Michael
>>
>> --
>> Michael Hausenblas
>> Ireland, Europe
>> http://mhausenblas.info/
>>
>> On 14 Oct 2012, at 18:19, Ted Dunning wrote:
>>
>> > So it sounds like I should create a sandbox area for components that we
>> > haven't integrated yet.
>> >
>> > Then I (or other committers) can commit to this area and as the
>> components
>> > come together, we can promote the best of each alternative to the real
>> deal.
>> >
>> > On Sun, Oct 14, 2012 at 7:04 AM, Michael Hausenblas <
>> > michael.hausenblas@gmail.com> wrote:
>> >
>> >>
>> >>> Michael,
>> >>>
>> >>> You have the web front end ready it sounds like.  Can you provide us
a
>> >>> walk-through?
>> >>
>> >>
>> >> FYI: I've deployed a new version of the front-end at
>> >> http://srvgal85.deri.ie/apache-drill/
>> >>
>> >> The improvements [1] include handling of data sources, more project
>> >> handling stuff and rendering of the results. If you click the
>> 'Tutorial'
>> >> button you get a sort of mini-help how to use it.
>> >>
>> >> I plan to do the screen cast against this version, should be available
>> via
>> >> YouTube by EoB (my time) tomorrow ...
>> >>
>> >> Cheers,
>> >>           Michael
>> >>
>> >> [1]
>> https://github.com/mhausenblas/apache-drill-frontend/commits/master
>> >>
>> >> --
>> >> Michael Hausenblas
>> >> Ireland, Europe
>> >> http://mhausenblas.info/
>> >>
>> >> On 11 Oct 2012, at 08:59, Ted Dunning wrote:
>> >>
>> >>> 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