SuccessChanges

Summary

  1. [SPARK-30401][SQL] Call `requireNonStaticConf()` only once in `set()` (details)
  2. [SPARK-27871][SQL][FOLLOW-UP] Format config name to follow the other (details)
Commit b316d373658089a6fc52938eb84e5be6b97734a1 by gurwls223
[SPARK-30401][SQL] Call `requireNonStaticConf()` only once in `set()`
### What changes were proposed in this pull request? Calls of
`requireNonStaticConf()` are removed from the `set()` methods in
RuntimeConfig because those methods invoke `def set(key: String, value:
String): Unit` where `requireNonStaticConf()` is called as well.
### Why are the changes needed? To avoid unnecessary calls of
`requireNonStaticConf()`.
### Does this PR introduce any user-facing change? No
### How was this patch tested? By existing tests from `SQLConfSuite`
Closes #27062 from MaxGekk/call-requireNonStaticConf-once.
Authored-by: Maxim Gekk <max.gekk@gmail.com> Signed-off-by: HyukjinKwon
<gurwls223@apache.org>
The file was modifiedsql/core/src/main/scala/org/apache/spark/sql/RuntimeConfig.scala (diff)
Commit 90794b617c9e4fda331b8602538a589590fac4f2 by gurwls223
[SPARK-27871][SQL][FOLLOW-UP] Format config name to follow the other
boolean conf naming convention
### What changes were proposed in this pull request?
Change config name from `spark.sql.optimizer.reassignLambdaVariableID`
to `spark.sql.optimizer.reassignLambdaVariableID.enabled`.
### Why are the changes needed?
To follow the other boolean conf naming convention.
### Does this PR introduce any user-facing change?
No, it's newly added in Spark 3.0.
### How was this patch tested?
Pass Jenkins.
Closes #27063 from Ngone51/SPARK-27871-FOLLOWUP.
Authored-by: yi.wu <yi.wu@databricks.com> Signed-off-by: HyukjinKwon
<gurwls223@apache.org>
The file was modifiedsql/catalyst/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala (diff)