[
https://issues.apache.org/jira/browse/SPARK-60385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uroš Bojanić resolved SPARK-60385.
----------------------------------
Fix Version/s: 4.4.0
Resolution: Fixed
Issue resolved by pull request 59634
[https://github.com/apache/spark/pull/59634]
> Pass JDBCOptions to JdbcUtils.getSchema instead of individual timestamp flags
> -----------------------------------------------------------------------------
>
> Key: SPARK-60385
> URL: https://issues.apache.org/jira/browse/SPARK-60385
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 4.4.0
> Reporter: Aleksandar Trajković
> Assignee: Aleksandar Trajković
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.4.0
>
>
> JdbcUtils.getSchema and its private helper getCatalystType take
> isTimestampNTZ and preferTimestampNanos as separate boolean parameters. Every
> caller already holds a JDBCOptions and unpacks those two fields from it. Pass
> JDBCOptions instead, so new read options that affect type mapping don't keep
> widening the signature. No user-facing change. The column metadata keys that
> dialects read are unchanged.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
