[HIVE-21142] Druidhandler may miss results when time constrainted by and/ors

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0.0-alpha-1
• Component/s: Druid integration
• Assignee: Zoltan Haindrich
• Reporter: Zoltan Haindrich
• Created: 22/Jan/19 10:42
• Updated: 17/Nov/22 08:54
• Resolved: 17/Jun/19 08:42

Description

For the following query:

FROM druid_table_alltypesorc
WHERE ('1968-01-01 00:00:00' <= `__time` AND `__time` <= '1970-01-01 00:00:00')
    OR ('1968-02-01 00:00:00' <= `__time` AND `__time` <= '1970-04-01 00:00:00') ORDER BY `__time` ASC LIMIT 10;

the druid query is:

druid.query.json {"queryType":"scan","dataSource":"default.druid_table_alltypesorc","intervals":["1900-01-01T00:00:00.000Z/1968-02-01T08:00:00.001Z"],"virtualColumns":[{"type":"expression","name":"vc","expression":"\"__time\"","outputType":"LONG"}],"columns":["vc"],"resultFormat":"compactedList"}

which has an invalid interval: "intervals":["1900-01-01T00:00:00.000Z/1968-02-01T08:00:00.001Z" which prevents valid results from 1969 to appear.

note: using between the interval is handled correctly

Issue Links

• relates to: CALCITE-2802 Druid adapter: Usage of range conditions like "2010-01-01 < timestamp" leads to incorrect results