feat: preserve Arrow Date(MILLISECOND) columns through Spark roundtrip#464
Open
summaryzb wants to merge 1 commit intolance-format:mainfrom
Open
feat: preserve Arrow Date(MILLISECOND) columns through Spark roundtrip#464summaryzb wants to merge 1 commit intolance-format:mainfrom
summaryzb wants to merge 1 commit intolance-format:mainfrom
Conversation
Change-Id: I832408fa941c1ebdf59a61307bfcda4e183ba64f
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
1 participant
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.
Preserve Arrow
Date(MILLISECOND)columns through Spark read-write roundtrips by carrying the original Arrow date unit in Spark field metadata. Without this change, Lance datasets created by PyArrow or other non-Spark sources that useDate(MILLISECOND)would silently downgrade toDate(DAY)when written back through Spark, corrupting interoperability with downstream consumers that expect millisecond-unit dates.