[CALCITE-1579] Druid adapter: wrong semantics of groupBy query limit with granularity

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.11.0
• Fix Version/s: 1.12.0
• Component/s: druid-adapter
• Assignee: Julian Hyde
• Reporter: Jesús Camacho Rodríguez
• Created: 16/Jan/17 15:39
• Updated: 27/Feb/24 22:15
• Resolved: 20/Jan/17 00:06

Description

Similar to CALCITE-1578, but for GroupBy queries. Limit is applied per granularity unit, not globally for the query.

Currently, the following SQL query infers granularity 'day' for Druid groupBy and pushes the limit, which is incorrect.

SELECT i_brand_id, floor_day(`__time`), max(ss_quantity), sum(ss_wholesale_cost) as s
FROM store_sales_sold_time_subset
GROUP BY i_brand_id, floor_day(`__time`)
ORDER BY s
LIMIT 10;

Issue Links

• relates to: HIVE-15637 Hive/Druid integration: wrong semantics of groupBy query limit with granularity