Dremio's query optimizer can accelerate a query against tables or views by using one or more reflections to partially or entirely satisfy that query, rather than processing the raw data in the underlying data source. Queries do not need to reference reflections directly. Instead, Dremio rewrites queries on the fly to use the reflections that satisfy them.
When Dremio receives a query, it determines first whether any reflections have at least one table in common with the tables and views that the query references. If any reflections do, Dremio evaluates them to determine whether they satisfy the query. Then, if any reflections do satisfy the query, Dremio generates a query plan that uses them.
Dremio then compares the cost of the plan to the cost of executing the query directly against the tables, and selects the plan with the lower cost. Finally, Dremio executes the selected query plan. Typically, plans that use one or more reflections are less expensive than plans that run against raw data. To get the best results from using reflections, see Best Practices for Creating Raw and Aggregation Reflections.
Much of this is covered in the above video so if you process things better in audio-visual than in print, you have your options. I've heard some gossip that Jenkins was going to issue a "new definition" of "transmedia": this is no where near as dramatic an overhaul as that, just some clarifications and reflections about definitions. This definition still covers, more or less, what I mean by transmedia storytelling:
The video reflections for the daily readings are getting a fresh look and feel. As we continue to provide a video reflection each day, we are making changes in our video service to be compatible with more devices.
aa06259810