Hey there, This is great news. I'm glad that your finding value in what we have built thus far. Couple of thoughts:
>> Regarding prototype/exec/ref and future plans Exec/ref will probably continue to move along slowly. We're now starting to focus a lot more on the full distributed execution engine and so future optimizations will probably be focused on that portion of the project. Hopefully you'll see more code evidence of this soon. >> Regarding your own work Even if you're building stuff that may not be able to be directly contributed back, it would be great if you could use a github fork so we can see whether anything can be pulled back. Let me know specific foci you have as well any problems or questions you have and we'll try to do our best as community to help you out. Thanks, Jacques On Wed, Mar 20, 2013 at 12:32 AM, Lisen Mu <[email protected]> wrote: > Hi, > > We are building a prototype system aiming to process query against > different data sources, based on drill's prototype. Thanks to all the great > work done so far in drill, it actually works for us. And I'm also pleased > to see all the effort being done to make progress in various aspects of > drill. > > In the near future we will continue mainly optimizing our prototype system. > we are also pleased to contribute back to drill project whatever we come > across and could help maturing drill, may it be bug reports, patches, > testcases, etc. > > On the other hand, in order to fit our production need ASAP, we have built > some modules in a non-generic way (optimizer and storage engine etc.), > based on drill's current master state. we're planning to adopt future > progress of these modules of drill, and willing to contribute to make that > future nearer. > > Also advices is most appreciated: what's your future plan about > prototype/exec/ref? we are going to do some optimization work based on it > soon. > > Thanks, >
