[SPARK-49763] [CSV] [SQL] [Schema Detection] #48220
Closed
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.
What changes were proposed in this pull request?
[CSV Reader] Add Flag to Control Inference of Time-Only Columns as String or Timestamp During Schema Detection
Why are the changes needed?
By default, Spark converts time-only columns to Timestamp type, which can lead to unintended behavior in certain use cases. This new flag will allow users to specify whether time-only columns should be inferred as Timestamp or as String.
This flag
inferStringTypeForTimeOnlyColumncan be supplied while reading the CSV files , true will infer as String, default behaviour is false and infers as timestamp.[Default/"inferStringTypeForTimeOnlyColumn" -> "false"]
["inferStringTypeForTimeOnlyColumn" -> "true"]
Does this PR introduce any user-facing change?
No
How was this patch tested?
Unit tests.
Was this patch authored or co-authored using generative AI tooling?
No