Probably time to do an update, the Prezi doc should be public, feel free to make changes!
Tim On Tue, Apr 28, 2015 at 1:26 PM, Eric Fukuda <[email protected]> wrote: > This web page really helps to understand how Drill works! > Thank you so much! > > On Tue, Apr 28, 2015 at 12:23 PM, Aditya <[email protected]> wrote: > >> Sometime back, Tim had put together a nice presentation[1], which should >> get you started at lease from the flow of control through Drill and should >> help you to discover the relevant code. >> >> Some of it may be outdated but the overall scheme of things remain same. >> >> >> [1] >> >> https://tnachen.wordpress.com/2013/11/05/lifetime-of-a-query-in-drill-alpha-release/ >> >> On Tue, Apr 28, 2015 at 9:06 AM, Eric Fukuda <[email protected]> wrote: >> >> > I'm trying to figure out where in the code: >> > - the JDBC client sends the query to a drillbit >> > - a drillbit receives the partitioned query >> > - a drillbit sends and receives the data to and from another drillbit >> > >> > I'm trying to take out the intermediate data between drillbits and write >> it >> > to a file. >> > >> > Thank you for your help. >> > >> > >> > On Tue, Apr 28, 2015 at 11:48 AM, Ted Dunning <[email protected]> >> > wrote: >> > >> > > I don't think that such a diagram exists. >> > > >> > > There are a number of slide shows around and there is some discussion >> of >> > > the architecture of Drill. Understanding how the system converts SQL >> to >> > a >> > > logical plan, to a physical plan and then to an execution plan is the >> > first >> > > step of understanding. >> > > >> > > Can you say more about what you want to know? Drill is a large code >> base >> > > and it helps to have an intention before starting to read. >> > > >> > > >> > > >> > > On Tue, Apr 28, 2015 at 8:27 AM, Eric Fukuda <[email protected]> >> > wrote: >> > > >> > > > Hi, I'm new to Drill and playing with it for a few days. I want to >> see >> > > > what's happening in the code, but it's not easy for a novice to >> > > understand. >> > > > Is there a low level design document like class diagram that can help >> > me >> > > > understand how the code works? >> > > > >> > > >> > >>
