[jira] [Updated] (SPARK-58864) Suggest customSchema / custom JdbcDialect in the UNRECOGNIZED_SQL_TYPE error

["Dongjoon Hyun (Jira)" <ji...@apache.org>]

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

Dongjoon Hyun updated SPARK-58864:
----------------------------------
        Parent: SPARK-58540
    Issue Type: Sub-task  (was: Bug)

>  Suggest customSchema / custom JdbcDialect in the UNRECOGNIZED_SQL_TYPE error
> -----------------------------------------------------------------------------
>
>                 Key: SPARK-58864
>                 URL: https://issues.apache.org/jira/browse/SPARK-58864
>             Project: Spark
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions: 4.3.0
>            Reporter: Ganesha S
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.4.0
>
>
> When the JDBC data source reads a column whose SQL type it cannot map to a Catalyst type, it fails with `UNRECOGNIZED_SQL_TYPE`:
> {code:java}
> Unrecognized SQL type - name: <typeName>, id: <jdbcType>.{code}
> The message states what failed but gives no remedy, so users have to read the source or open a support request to get past it. Both fixes already exist: the customSchema read option lets the user explicitly map the column, and a user-registered JdbcDialect can handle the type. This condition is only thrown from the JDBC read path (JdbcUtils.getCatalystType), so JDBC-specific guidance is appropriate.
> Proposed: append a guidance sentence to the UNRECOGNIZED_SQL_TYPE error condition



--
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