Hi So it seems right now the query is designed to return 0 rows. The query is there just to demonstrate the fallback feature.
Cube query is cube select customer_city_name, store_cost from sales where time_range_in(order_time, '2015-04-13-03', '2015-04-13-04') Driver query comes out to be SELECT (customer_city.name), sum((sales.store_cost)) FROM a.local_sales_aggr_fact2 sales join a.local_city_table customer_city on sales.customer_city_id = customer_city.id and (customer_city.dt = 'latest') WHERE (((((sales.dt) = '2015-04-13-04') or ((sales.dt) = '2015-04-13-05')) and ((sales.order_time) >= '2015-04-13 03:00:00') and ((sales.order_time) < '2015-04-13 04:00:00'))) GROUP BY (customer_city.name) Then I modified the driver query and ran: SELECT (customer_city.name), sales.order_time, sales.store_cost FROM a.local_sales_aggr_fact2 sales join a.local_city_table customer_city on sales.customer_city_id = customer_city.id and (customer_city.dt = 'latest') WHERE (((((sales.dt) = '2015-04-13-04') or ((sales.dt) = '2015-04-13-05')))) Found the following results: Bangalore^A2015-04-13 00:00:00^A0.0 Hyderabad^A2015-04-13 00:00:00^A2.0 It's apparent that both the rows will be filtered out by the translated query. I'll look deeper and replace the example query with something that demonstrates the fallback feature and also returns non-empty results. Let us know if you have any confusion understanding the feature itself. I think the video should have covered it. Regards
