Repository navigation
Spark, Databricks: parse multi-unit interval literals - #2616
Draft
moshap-firebolt wants to merge 2 commits into
Draft
moshap-firebolt wants to merge 2 commits into
moshap-firebolt wants to merge 2 commits into
Conversation
Spark's multi-units interval syntax lets the string carry its own units, as in INTERVAL '1 YEAR 2 DAYS 3 HOURS', so no unit follows the literal. Databricks Runtime parses with the same grammar. A unit after a literal is still read; the expression form this gives up (INTERVAL 1 + 1 DAY) is not Spark syntax.
moshap-firebolt
marked this pull request as draft
October 6, 2026 21:34
Spark's multi-units interval syntax lists several value / unit pairs, INTERVAL 10 YEAR 20 MONTH, documented as the same as the string form INTERVAL '10 YEAR 20 MONTH'. A new supports_interval_multi_units hook, enabled for SparkSqlDialect and DatabricksDialect, reads the extra pairs into that string form, so the AST is unchanged.
moshap-firebolt
force-pushed
the
moshap/upstream-interval-multi-units
branch
from
October 6, 2026 21:35
e3732a5 to
f696fd3
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2616 +/- ##
==========================================
+ Coverage 81.14% 81.16% +0.01%
==========================================
Files 42 42
Lines 33736 33766 +30
Branches 33736 33766 +30
==========================================
+ Hits 27376 27407 +31
+ Misses 2797 2795 -2
- Partials 3563 3564 +1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #2614, whose commit this branch includes; only the last commit is new. It needs #2614 because the string form below has no unit, which Spark and Databricks reject until #2614 lands. I will rebase onto
mainonce #2614 merges.Spark's multi-units interval syntax lists several value / unit pairs,
INTERVAL 10 YEAR 20 MONTH, documented as equivalent toINTERVAL '10 YEAR 20 MONTH'.This adds
Dialect::supports_interval_multi_units, enabled forSparkSqlDialectandDatabricksDialect. When set,parse_intervalreads the extra pairs into that string form, so the AST is unchanged. A single unit, or a unit followed by something else (INTERVAL 3 DAY + 1), parses as before. Tests insqlparser_common.rscover dialects with and without the hook.