> On Jan 23, 2017, at 12:14 PM, Gian Merlino <[email protected]> wrote: > > I bet you could also write some cool Calcite rules to make a phantom > "dimdate" table available, and convert joins on that table into application > of Druid native time functions on the base table. That'd allow the first > SQL query to work in an efficient way.
That would indeed be cool (and useful). If you define a Calcite lattice of, say, a sales and time_by_day tables, backed by a Druid table, then Calcite will endeavor to convert join queries into queries on the Druid table. Those Druid queries will not be joins. Julian
