Hi All, Any thoughts on the DrillClient modularization/short term alternative?
Hari ---------- Forwarded message ---------- From: Srihari Srinivasan <[email protected]> Date: Tue, Jul 23, 2013 at 10:33 PM Subject: Re: Meeting today To: [email protected] Cc: [email protected] Hi, 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 branch<https://github.com/srihari/incubator-drill>. Its still a clone of the execwork branch. -- Hari On Fri, Jul 12, 2013 at 9:22 PM, Jacques Nadeau <[email protected]> wrote: > Sounds good to me. > > On Fri, Jul 12, 2013 at 7:07 AM, Srihari Srinivasan > <[email protected]> wrote: > > HI Folks, > > > > Moving on I am trying to implement the functionality that creates a query > > via the REST interface. I have a question w.r.t its implementation. One > way > > to implement this would be via the DrillClient class by calling its > > runQuery(QueryType) method as illustrated in TestDistributedFragmentRun. > > > > Does this approach make sense? Should we be considering any other > > alternatives? > > > > Hari >
