Repository navigation
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
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?
Closes #2723
Rationale for this change
from_unixtimecurrently relies on Spark expression fallback. Add native execution for common constant formats.What changes are included in this PR?
FromUnixTimeto a dedicatedSpark_FromUnixTimeextension function.yyyy-MM-dd HH:mm:ssformat, plus constantyyyy-MM-ddandyyyyMMdd.Dynamic or unsupported formats, regional time zones, LEGACY policy and complex seconds expressions retain Spark fallback. Column pruning conversion also remains unsupported.
Keep input casts and arithmetic in Spark fallback to preserve ANSI errors. Invalid constant formats use Spark operator fallback, including when all seconds are null.
Are there any user-facing changes?
Supported calls can run natively with
spark.auron.enableNativeDateTimeFunctions=true; this switch remains disabled by default.Column inputs also require
spark.auron.udf.singleChildFallback.enabled=true.How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?
Generated-by: OpenAI Codex (GPT-6)
ASF guidance: https://www.apache.org/legal/generative-tooling.html