INTERVAL 1 WEEK in SQL is wrong interval

The INTERVAL 1 WEEK syntax in SQL is resolving to PT1H.

Affected Version

Found in Apache Druid 33.0.0

Description

Most easily detected by running this SQL query in Unified Console Workbench:

SELECT 
  MILLIS_TO_TIMESTAMP(0) + INTERVAL 1 WEEK,
  MILLIS_TO_TIMESTAMP(0) + INTERVAL 2 WEEK

Expected Results:

EXPR$0,EXPR$1
1970-01-08T00:00:00.000Z,1970-01-15T00:00:00.000Z

Actual Results:

EXPR$0,EXPR$1
1970-01-01T01:00:00.000Z,1970-01-01T02:00:00.000Z

Just ran into the same problem on Druid 34.0.0:

SELECT
  CURRENT_TIMESTAMP AS now,
  CURRENT_TIMESTAMP - INTERVAL '7' DAYS AS last_week_correct,
  CURRENT_TIMESTAMP - INTERVAL '1' WEEK AS last_week_wrong
```

I can repro on Druid 34.0.0 — INTERVAL '1' WEEK resolves to PT1H instead of P7D. Looks like the WEEK unit is missing from the Calcite-to-Druid interval conversion (most other units land in the day path but WEEK falls through to hours). Going to dig in and send a PR with a SqlIntervalArithmeticTest covering WEEK alongside the existing DAY/MONTH cases.

fix: INTERVAL n WEEK in SQL resolves to seven days instead of one hour

Navigation Menu

Repository navigation

INTERVAL 1 WEEK in SQL is wrong interval #18665

Affected Version

Description

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

INTERVAL 1 WEEK in SQL is wrong interval #18665

Description

Affected Version

Description

Activity

christian-schlichtherle commented on Feb 10, 2026

barry3406 commented on Apr 11, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions