Skip to content

fix: add missing interval_day derivation expression#175

Merged
tokoko merged 1 commit into
substrait-io:mainfrom
thgschwind:fix_interval_day_expressions
Jun 10, 2026
Merged

fix: add missing interval_day derivation expression#175
tokoko merged 1 commit into
substrait-io:mainfrom
thgschwind:fix_interval_day_expressions

Conversation

@thgschwind

@thgschwind thgschwind commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

The _evaluate() function in derivation_expression.py now returns
Type(interval_day=Type.IntervalDay(...)) instead of raising an exception.

Fixes: #174

Signed-off-by: Thomas Gschwind <thg@zurich.ibm.com>
@CLAassistant

CLAassistant commented Jun 10, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@github-actions

Copy link
Copy Markdown

ACTION NEEDED

Substrait follows the Conventional Commits
specification
for
release automation.

The PR title and description are used as the merge commit message. Please update your PR title and description to match the specification.

@thgschwind thgschwind changed the title fix: added missing interval_day derivation expression fix: add missing interval_day derivation expression Jun 10, 2026
@tokoko tokoko merged commit 077859b into substrait-io:main Jun 10, 2026
20 of 24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

derivation_expression._evaluate() does not handle PrecisionIntervalDayContext

3 participants