[SPARK-40360] ALREADY_EXISTS and NOT_FOUND exceptions

[srielau]

What changes were proposed in this pull request?

This PR introduces the following error classes:

• PARTITIONS_ALREADY_EXIST
  Cannot ADD or RENAME TO partition(s) in table because they already exist.
  Choose a different name, drop the existing partition, or add the IF NOT EXISTS clause to tolerate a pre-existing partition

• PARTITIONS_NOT_FOUND
  The partition(s) cannot be found in table .
  Verify the partition specification and table name.
  To tolerate the error on drop use ALTER TABLE … DROP IF EXISTS PARTITION.

• ROUTINE_ALREADY_EXISTS
  Cannot create the function because it already exists.
  Choose a different name, drop or replace the existing function, or add the IF NOT EXISTS clause to tolerate a pre-existing function

• ROUTINE_NOT_FOUND
  The function cannot be found. Verify the spelling and correctness of the schema and catalog.
  If you did not qualify the name with a schema and catalog, verify the current_schema() output, or qualify the name with the correct schema and catalog.
  To tolerate the error on drop use DROP FUNCTION IF EXISTS

• SCHEMA_ALREADY_EXISTS
  Cannot create schema because it already exists.
  Choose a different name, drop the existing schema, or add the IF NOT EXISTS clause to tolerate pre-existing schema

• SCHEMA_NOT_EMPTY
  Cannot drop a schema because it contains objects.
  Use DROP SCHEMA ... CASCADE to drop the schema and all its objects.

• SCHEMA_NOT_FOUND
  The schema cannot be found. Verify the spelling and correctness of the schema and catalog.
  If you did not qualify the name with a catalog, verify the current_schema() output, or qualify the name with the correct catalog.
  To tolerate the error on drop use DROP SCHEMA IF EXISTS.

• TABLE_OR_VIEW_ALREADY_EXISTS
  Cannot create table or view 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

• TABLE_OR_VIEW_NOT_FOUND
  The table or view cannot be found. Verify the spelling and correctness of the schema and catalog.
  If you did not qualify the name with a schema, verify the current_schema() output, or qualify the name with the correct schema and catalog.
  To tolerate the error on drop use DROP VIEW IF EXISTS or DROP TABLE IF EXISTS.

• TEMP_TABLE_OR_VIEW_ALREADY_EXISTS
  Cannot create the temporary view because it already exists.
  Choose a different name, drop or replace the existing view, or add the IF NOT EXISTS clause to tolerate pre-existing views.

Also (for JDBC data sources):

• INDEX_ALREADY_EXISTS
  Cannot create the index because it already exists. .

• INDEX_NOT_FOUND
  Cannot find the index. .

Some background:

• We use ROUTINE over FUNCTION to be future proof, if/when PROCEDUREs appear.
• We coarsify around TABLE_OR_VIEW_NOT_FOUND and TABLE_OR_VIEW_ALREADY_EXISTS (getting rid of dedicated reason as RENAME TABLE, etc.
• We combine PARTITION and PARTITIONS errors
• I use SCHEMA religiously. A debate can be had whether/ho/when to return NAMESPACE

There is currently one failure caused by:

https://issues.apache.org/jira/browse/SPARK-40521
Hive based ALTER TABLE ADD PARTITION returns to many partitions in case of PARTITIONS_ALREADY_EXISTS.

Why are the changes needed?

We want to convert all error to use the error-class framework

Does this PR introduce any user-facing change?

Yes, we are moving away from "free txt" and consolidate errors is error-classes.json.
This hardens the QA and code allowing us to improve error messages without breaking changes

How was this patch tested?

Run existing QA suite

[AmplabJenkins]

Can one of the admins verify this patch?

[srielau]

@MaxGekk @cloud-fan
Since the last review I have:

• eliminated tolerance for not having context and added all the contexts
• removed replaced template error codes
• addressed minor comments
• added namespace related error messages in error-classes.json

What I have NOT done and need help with:

• One remaining failure where I don't know how to generate the correct fragment in a multimode test. I have reached out to @gengliangwang to assist
• Pull checkErrorTableNotFound() out of SparkFunSuite. In fact, in a way, its now worse because of new overloading for context
• Generate NAMESPACE error codes

[cloud-fan]

thanks, merging to master!

[anchovYu]

Should this be INDEX_ALREADY_EXISTS?

[MaxGekk]

This has been fixed in another PR as far as I remember. Please, check the master branch.