Ganesha S created SPARK-58864:
---------------------------------
Summary: 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: Bug
Components: SQL
Affects Versions: 4.3.0
Reporter: Ganesha S
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: [email protected]
For additional commands, e-mail: [email protected]
