Add datafusion.extract #959
Merged
Conversation
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.
Which issue does this PR close?
Completes a task in #463
Rationale for this change
This PR introduces the implementation of the EXTRACT function, which allows extracting specific temporal units (e.g., YEAR, MONTH, DAY) from date or timestamp fields. It is an alias of
date_part.What changes are included in this PR?
Functionality:
Adds the implementation of the EXTRACT subscalar function, it supports extracting temporal units like YEAR, MONTH, DAY, etc., from supported date, timestamp, and time data types.
Tests:
Adds tests for EXTRACT.
Are there any user-facing changes?
Yes, this PR adds the EXTRACT function to the API, enabling users to perform temporal extraction operations directly.