[CALCITE-5222] Support more EXTRACT field values (or allow arbitrary in parse?)

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Fix Version/s: 1.32.0
• Assignee: Unassigned
• Reporter: Steven Talbot
• Created: 28/Jul/22 16:25
• Updated: 10/Sep/22 08:42
• Resolved: 29/Jul/22 13:22

Description

E.g. a number of BigQuery EXTRACTs from https://cloud.google.com/bigquery/docs/reference/standard-sql/timestamp_functions#extract do not parse with the babel parser

EXTRACT(DAYOFWEEK FROM <date_col>)
EXTRACT(TIME FROM <date_col>)

(also DATE, DATETIME, DAYOFYEAR... there may be others)

Other dialects may have similar problems, e.g. "EXTRACT(JULIAN...)" in Postgres looks like it wouldn't parse either.

Calcite chasing down every value ever implemented by a DB vendor here seems like it might be too tall of a task, but perhaps allowing for an arbitrary keyword in that syntactic position, and then users of the parser would have to handle it if the parse of the EXTRACT comes out with an arbitrary symbol, rather than a TimeUnit enum value for one of the known EXTRACT fields.

Issue Links

• duplicates: CALCITE-5143 Allow custom time unit abbreviations in FLOOR, CEIL, EXTRACT, DATE_PART, DATEADD, DATEDIFF and similar functions
• duplicates: CALCITE-5155 Custom time frames