[CALCITE-5147] Allow DATE, TIME, TIMESTAMP, INTERVAL literals in BigQuery dialect

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.31.0
• Labels: pull-request-available
• Assignee: Wenrui Meng
• Reporter: Steven Talbot
• Created: 10/May/22 17:18
• Updated: 30/Nov/22 17:42
• Resolved: 06/Jun/22 22:15

Description

Parser configured with BigQuery dialect cannot parse timestamp literal.

It looks like CALCITE-4247 creates a special string literal token for BigQuery. But that means that (AFAICT) Parser.jj then does not find the expected token type after a TIMESTAMP to make a timestamp literal, so something as simple as

SqlParser.create("SELECT TIMESTAMP '2018-02-17 13:22:04'", BigQuerySqlDialect.DEFAULT.configureParser(SqlParser.config())).parseQuery() 

fails.

Probably most other places in Parser.jj that use the "<QUOTED_STRING>" token suffer from the same issue.

Issue Links

• is related to: CALCITE-4247 When parsing SQL in BigQuery dialect, character literals may be enclosed in single- or double-quotes, and use backslashes as escapes
• is related to: CALCITE-5159 ARRAY string constructor, and implicit cast from string literal (enabled in PostgreSQL conformance)
• links to: GitHub Pull Request #2823