Skip to content

feat: improve pythonic interface on date/time functions#1563

Draft
timsaucer wants to merge 1 commit into
apache:mainfrom
timsaucer:feat/pythonic-datetime-coercion
Draft

feat: improve pythonic interface on date/time functions#1563
timsaucer wants to merge 1 commit into
apache:mainfrom
timsaucer:feat/pythonic-datetime-coercion

Conversation

@timsaucer
Copy link
Copy Markdown
Member

Which issue does this PR close?

Ongoing ergonomic improvements, but no specific issue.

Rationale for this change

This PR makes a lot of the date/time functions take strings or integer when appropriate. This makes the code cleaner so that users don't always have to wrap these in a lit() call.

What changes are included in this PR?

Python changes only. When a str or int (as appropriate) is found, coerce it to a literal.

Are there any user-facing changes?

Prior code works as is. This simply makes newer code easier to write.

Widen date/time scalar function signatures to accept native Python
``str``/``int`` literals alongside ``Expr``:

- ``date_bin``: ``stride``, ``source``, ``origin`` accept ``Expr | str``.
- ``make_date``, ``make_time``: components accept ``Expr | int``.
- ``to_date``, ``to_time``, ``to_timestamp``, ``to_timestamp_{millis,
  micros,nanos,seconds}``, ``to_unixtime``: ``*formatters`` accept
  ``Expr | str``.

Add ``coerce_to_expr_list`` public helper in ``datafusion.expr`` mirroring
``coerce_to_expr`` / ``ensure_expr_list`` for variadic call sites.
``date_bin`` uses ``Expr.string_literal`` directly because its planner
coerces ``Utf8`` (not ``Utf8View``) literals to ``Interval``/``Timestamp``.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.

1 participant