yaooqinn opened a new pull request, #40718:
URL: https://github.com/apache/spark/pull/40718
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://spark.apache.org/contributing.html
2. Ensure you have added or run the appropriate tests for your PR:
https://spark.apache.org/developer-tools.html
3. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP][SPARK-XXXX] Your PR title ...'.
4. Be sure to keep the PR description updated to reflect all changes.
5. Please write your PR title to summarize what this PR proposes.
6. If possible, provide a concise example to reproduce the issue for a
faster review.
7. If you want to add a new configuration, please read the guideline first
for naming configurations in
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
8. If you want to add or modify an error type or message, please read the
guideline first in
'core/src/main/resources/error/README.md'.
-->
### What changes were proposed in this pull request?
<!--
Please clarify what changes you are proposing. The purpose of this section
is to outline the changes and how this PR fixes the issue.
If possible, please consider writing useful notes for better and faster
reviews in your PR. See the examples below.
1. If you refactor some codes with changing classes, showing the class
hierarchy will help reviewers.
2. If you fix some SQL features, you can provide some references of other
DBMSes.
3. If there is design documentation, please add the link.
4. If there is a discussion in the mailing list, please add the link.
-->
This PR makes UNRECOGNIZED_SQL_TYPE print both the column type name and the
id.
### Why are the changes needed?
<!--
Please clarify why the changes are needed. For instance,
1. If you propose a new API, clarify the use case for a new API.
2. If you fix a bug, you can clarify why it is a bug.
-->
UNRECOGNIZED_SQL_TYPE prints the jdbc type id in the error message
currently. This is difficult for spark users to understand the meaning of this
kind of error, especially when the type id is from a vendor extension.
For example,
```java
org.apache.spark.SparkSQLException: Unrecognized SQL type -102
```
While -102 is nonstandard, it's hard to know what type it is
```
classOf[java.sql.JDBCType].getEnumConstants.foreach(t => println(t.getName +
"|" + t.getVendorTypeNumber))
BIT|-7
TINYINT|-6
SMALLINT|5
INTEGER|4
BIGINT|-5
FLOAT|6
REAL|7
DOUBLE|8
NUMERIC|2
DECIMAL|3
CHAR|1
VARCHAR|12
LONGVARCHAR|-1
DATE|91
TIME|92
TIMESTAMP|93
BINARY|-2
VARBINARY|-3
LONGVARBINARY|-4
NULL|0
OTHER|1111
JAVA_OBJECT|2000
DISTINCT|2001
STRUCT|2002
ARRAY|2003
BLOB|2004
CLOB|2005
REF|2006
DATALINK|70
BOOLEAN|16
ROWID|-8
NCHAR|-15
NVARCHAR|-9
LONGNVARCHAR|-16
NCLOB|2011
SQLXML|2009
REF_CURSOR|2012
TIME_WITH_TIMEZONE|2013
TIMESTAMP_WITH_TIMEZONE|2014
```
### Does this PR introduce _any_ user-facing change?
<!--
Note that it means *any* user-facing change including all aspects such as
the documentation fix.
If yes, please clarify the previous behavior and the change this PR proposes
- provide the console output, description and/or an example to show the
behavior difference if possible.
If possible, please also clarify if this is a user-facing change compared to
the released Spark versions or within the unreleased branches such as master.
If no, write 'No'.
-->
yes, the unrecognized jdbc type error will also print the type name
For example,
```java
org.apache.spark.SparkSQLException: Unrecognized SQL type - name: TIMESTAMP
WITH LOCAL TIME ZONE, id: -102
```
### How was this patch tested?
<!--
If tests were added, say they were added here. Please make sure to add some
test cases that check the changes thoroughly including negative and positive
cases if possible.
If it was tested in a way different from regular unit tests, please clarify
how you tested step by step, ideally copy and paste-able, so that other
reviewers can test and check, and descendants can verify in the future.
If tests were not added, please describe why they were not added and/or why
it was difficult to add.
If benchmark tests were added, please run the benchmarks in GitHub Actions
for the consistent environment, and the instructions could accord to:
https://spark.apache.org/developer-tools.html#github-workflow-benchmarks.
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
