Adding to Rahul, You can also take a look at Calcite [2], (which Drill uses for SQL parsing + query optimization) and a relevant thread I found on the mailing list [3].
[2] https://calcite.apache.org/ [3] http://mail-archives.apache.org/mod_mbox/drill-dev/201506.mbox/%3ccafydvvlkkmizeucfyfyxyge_5kzvopds0ozyabub54ncl7k...@mail.gmail.com%3E On Tue, Jul 5, 2016 at 10:39 AM, rahul challapalli < [email protected]> wrote: > For a start, below is the relevant piece from the documentation [1]. You > can also prepend any query with "explain plan for" to view the exact plan > generated by Drill's Optimizer. > > • Optimizer: Drill uses various standard database optimizations such as > rule based/cost based, as well as data locality and other optimization > rules exposed by the storage engine to re-write and split the query. The > output of the optimizer is a distributed physical query plan that > represents the most efficient and fastest way to execute the query across > different nodes in the cluster. > > [1] https://drill.apache.org/architecture/ > > On Tue, Jul 5, 2016 at 7:59 AM, Benamor, Adel <[email protected]> > wrote: > > > Hello, > > I'm new in the utilization of data virtualization and I try to > understand > > the running of Apache Drill. > > I browsed the documentation but I didn't understand how is the running of > > the optimizer. > > Indeed, I learned that it's a cost-base optimizer, but nothing else. > > I want to know how the optimizer works ? > > > > Thanks for your help > > Warm regards > > Adel BENAMOR > > > > >
