drill-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Srihari Srinivasan <ssrin...@thoughtworks.com>
Subject Re: Meeting today
Date Tue, 23 Jul 2013 17:03:09 GMT

Quick note on what we discussed w.r.t the REST API.

I am at a point where to submit a query (logical for now) to the Drillbit I
need an instance of the DrillClient class from the Query REST resource.
DrillClient is currently part of the java-exec module. I've pulled out the
jersey/jetty stuff into its own mvn module to keep the concerns separate.

So the really question is - Is now a good time to pull out DrillClient and
its dependencies into its own client module? That way http-engine can just
depend on the client lib. Having this will be a huge help as it can
potentially keep a parallel stream of working going.

Any other ideas/suggestions?

Jason - This is the link to my github
Its still a clone of the execwork branch.

-- Hari

On Tue, Jul 23, 2013 at 9:22 PM, Jacques Nadeau <jacques@apache.org> wrote:

> Hey guys, as mentioned last week,  I won't be at the Hangout today.   That
> said, here are a couple of things that I'd love to hear about.
> -Parquet reader status
> -JSON scanner implementation..  On rr at least two tests are currently
> failing and marked ignore. How do we fix
> -any update on writing physical tpc-h queries?
> -rest update
> -exchange sender
> -anybody want to start implementing DrillFuncs?
> -applying rest of optiq rels
> -Jason on getting a sql select where query to run
> I'll report back after Oscon.
> regards,
> Jacques

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