You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/10/20 09:38:00 UTC

[jira] [Updated] (SPARK-60385) Pass JDBCOptions to JdbcUtils.getSchema instead of individual timestamp flags

     [ https://issues.apache.org/jira/browse/SPARK-60385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated SPARK-60385:
-----------------------------------
    Labels: pull-request-available  (was: )

> 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ć
>            Priority: Major
>              Labels: pull-request-available
>
> 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: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org