[spark] Add legacy timestamp mapping option#8433
Merged
JingsongLi merged 1 commit intoJul 3, 2026
Merged
Conversation
kerwin-zk
force-pushed
the
fix-spark-legacy-timestamp-mapping
branch
from
3526c27 to
f3cd830
Compare
YannByron
approved these changes
Jul 3, 2026
Contributor
|
+1 |
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
3 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.
Purpose
Add
spark.paimon.legacy-timestamp-mapping.enabledfor Spark 3.4+ users who need to expose PaimonTIMESTAMPas SparkTIMESTAMPinstead ofTIMESTAMP_NTZ. The option is disabled by default, so existing Spark 3.4+ behavior is unchanged.When enabled, Paimon reuses the existing legacy timestamp conversion path. This helps workloads migrating from Spark 3.3 keep expressions such as
unix_timestamp(ts)followed byfrom_unixtime(...)consistent with their previous behavior.Tests
CI