[SPARK-40792] Helper object to get SQL configs for errors

[vitaliili-db]

What changes were proposed in this pull request?

Add a helper object to get SQL config keys for errors.

Why are the changes needed?

Allows injection of vendor specific SQL config keys, e.g. Databricks ansi_mode instead of spark.sql.ansi.enabled

Does this PR introduce any user-facing change?

No

How was this patch tested?

Careful review and existing unit tests.

[MaxGekk]

Allows injection of vendor specific SQL config keys, e.g. Databricks ansi_mode instead of spark.sql.ansi.enabled

@vitaliili-db Can't you just add an alternative for the config, see for example

spark/sql/catalyst/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala

Line 3617 in 8251f87

.withAlternative("spark.sql.legacy.parquet.int96RebaseModeInWrite")

[vitaliili-db]

Allows injection of vendor specific SQL config keys, e.g. Databricks ansi_mode instead of spark.sql.ansi.enabled

@vitaliili-db Can't you just add an alternative for the config, see for example

spark/sql/catalyst/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala

Line 3617 in 8251f87

.withAlternative("spark.sql.legacy.parquet.int96RebaseModeInWrite")

@MaxGekk For defining config withAlternative will work, but this logic is for retrieval. I.e. we want to show correct configuration key in error message depending in which context an error occurred.

[AmplabJenkins]

Can one of the admins verify this patch?

[MaxGekk]

I.e. we want to show correct configuration key in error message depending in which context an error occurred.

Can you do the replacement in more centralised way? For example, override the getMessageParameters() method and replace the config there? I just worry that we will forget to wrap the config in the future in some places, and your changes bring additional overhead during review.