[SPARK-48618][SQL] Utilize the ErrorCode and SQLState returned in SQLException to make errors more accurate

[panbingkun]

What changes were proposed in this pull request?

The pr aims to use the ErrorCode and SQLState returned in SQLException to make errors more accurate.

Why are the changes needed?

• eg for mysql

  withTable(s"$catalogName.tbl1", s"$catalogName.tbl2") {
        sql(s"CREATE TABLE $catalogName.tbl1 (col1 INT, col2 INT)")
        sql(s"CREATE TABLE $catalogName.tbl2 (col1 INT, col2 INT)")
        sql(s"ALTER TABLE $catalogName.tbl2 RENAME TO tbl1")
      }
  

• Before:

  [FAILED_JDBC.UNCLASSIFIED] Failed JDBC jdbc: on the operation: Failed table renaming from tbl2 to tbl1 SQLSTATE: 
  HV000
  org.apache.spark.sql.AnalysisException: [FAILED_JDBC.UNCLASSIFIED] Failed JDBC jdbc: on the operation: Failed table 
  renaming from tbl2 to tbl1 SQLSTATE: HV000
  	  at org.apache.spark.sql.jdbc.JdbcDialect.classifyException(JdbcDialects.scala:767)
      at org.apache.spark.sql.jdbc.JdbcDialect.classifyException(JdbcDialects.scala:751)
      at org.apache.spark.sql.jdbc.MySQLDialect.classifyException(MySQLDialect.scala:348)
      at org.apache.spark.sql.execution.datasources.jdbc.JdbcUtils$.classifyException(JdbcUtils.scala:1271)
      at org.apache.spark.sql.execution.datasources.v2.jdbc.JDBCTableCatalog.$anonfun$renameTable$1(JDBCTableCatalog.scala:125)
      at org.apache.spark.sql.execution.datasources.v2.jdbc.JDBCTableCatalog.$anonfun$renameTable$1$adapted(JDBCTableCatalog.scala:116)
      at org.apache.spark.sql.execution.datasources.jdbc.JdbcUtils$.withConnection(JdbcUtils.scala:1279)
  

• After:

  [TABLE_OR_VIEW_ALREADY_EXISTS] Cannot create table or view `tbl1` because it already exists.
  Choose a different name, drop or replace the existing object, or add the IF NOT EXISTS clause to tolerate pre-existing 
  objects. SQLSTATE: 42P07
  org.apache.spark.sql.catalyst.analysis.TableAlreadyExistsException: [TABLE_OR_VIEW_ALREADY_EXISTS] Cannot create table or view `tbl1` because it already exists.
  Choose a different name, drop or replace the existing object, or add the IF NOT EXISTS clause to tolerate pre-existing objects. SQLSTATE: 42P07
      at org.apache.spark.sql.errors.QueryCompilationErrors$.tableAlreadyExistsError(QueryCompilationErrors.scala:2643)
      at org.apache.spark.sql.jdbc.MySQLDialect.classifyException(MySQLDialect.scala:343)
      at org.apache.spark.sql.execution.datasources.jdbc.JdbcUtils$.classifyException(JdbcUtils.scala:1271)
      at org.apache.spark.sql.execution.datasources.v2.jdbc.JDBCTableCatalog.$anonfun$renameTable$1(JDBCTableCatalog.scala:125)
      at org.apache.spark.sql.execution.datasources.v2.jdbc.JDBCTableCatalog.$anonfun$renameTable$1$adapted(JDBCTableCatalog.scala:116)
      at org.apache.spark.sql.execution.datasources.jdbc.JdbcUtils$.withConnection(JdbcUtils.scala:1279)
  

• Aligning similar logic to PostgresDialect
  

  spark/sql/core/src/main/scala/org/apache/spark/sql/jdbc/PostgresDialect.scala

  Lines 273 to 275 in 08e741b

  	} else if (errorClass == "FAILED_JDBC.RENAME_TABLE") {
  	val newTable = messageParameters("newName")
  	throw QueryCompilationErrors.tableAlreadyExistsError(newTable)

Does this PR introduce any user-facing change?

Yes, End users will accurately know the cause of the error.

How was this patch tested?

Add new UT.

Was this patch authored or co-authored using generative AI tooling?

No.

[panbingkun]

ref:

errorCode: 955, sqlState: 42000, message: ORA-00955: name is already used by an existing object
https://docs.oracle.com/error-help/db/ora-00955/, errorClass: FAILED_JDBC.RENAME_TABLE, messageParameters: Map(url -> jdbc:oracle:thin:system/Th1s1sThe0racle#Pass@//10.1.0.20:38407/freepdb1, oldName -> `tbl2`, newName -> `tbl1`),description: Failed table renaming from tbl2 to tbl1

[panbingkun]

ref:

errorCode: 15335, sqlState: S0001, message: Error: The new name 'tbl1' is already in use as a object name and would cause a duplicate that is not permitted., errorClass: FAILED_JDBC.RENAME_TABLE, messageParameters: Map(url -> jdbc:sqlserver://10.1.0.20:38701;user=sa;***;encrypt=true;trustServerCertificate=true, oldName -> `tbl2`, newName -> `tbl1`),description: Failed table renaming from tbl2 to tbl1

[panbingkun]

ref:

errorCode: -601, sqlState: 42710, message: The name of the object to be created is identical to the existing name "DB2INST1.tbl1" of type "TABLE".. SQLCODE=-601, SQLSTATE=42710, DRIVER=4.33.31, errorClass: FAILED_JDBC.RENAME_TABLE, messageParameters: Map(url -> jdbc:db2://10.1.0.20:43213/foo:user=db2inst1;***;retrieveMessagesFromServerOnGetMessage=true;, oldName -> `tbl2`, newName -> `tbl1`),description: Failed table renaming from tbl2 to tbl1

[panbingkun]

https://www.ibm.com/docs/en/db2/11.5?topic=messages-sqlstate

[panbingkun]

cc @cloud-fan @yaooqinn @HyukjinKwon

[panbingkun]

also cc @MaxGekk

[MaxGekk]

+1, LGTM. Merging to master.
Thank you, @panbingkun.