Datetime and other temporal datatypes parsing #329
Merged
Conversation
Member
|
@gladysteh99 could you add some integration tests too for this so we can test in snowflake offline? |
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.
This PR fixes two bugs.
date(notdatetime) eg. "2023-01-08", polars support forfind_column_typewas parsing it incorrectly astimestamp, which leads to mismatch in sql format. This is now fixed, and added support fortime(%H:%M:%S) as well.datetimeor any of the temporal datatype, snowflake will not parse it properly as the time is stored as epoch time in parquet files. One of the fix is to allow users to specify a file format whereUSE_LOGICAL_TYPE = TRUE;to allow proper transfer. More information here.