huangxiaopingRD opened a new pull request, #53522: URL: https://github.com/apache/spark/pull/53522
### What changes were proposed in this pull request? Add version information to the configuration of Spark SQL. I sorted out some information show below. | Item name | Since version | JIRA ID | Commit ID | |-------|-------|-------|-------| | spark.sql.analyzer.preferColumnOverLcaInArrayIndex | 4.1.0 | [SPARK-53734](https://issues.apache.org/jira/browse/SPARK-53734) | https://github.com/apache/spark/commit/46ac78ea367cfa9a7acc04482770aaca33f5a575 | | spark.sql.analyzer.dontDeduplicateExpressionIfExprIdInOutput | 4.1.0 | [SPARK-53098](https://issues.apache.org/jira/browse/SPARK-53098) | https://github.com/apache/spark/commit/4a2ce9f7b0df677707b0f262afc492ebf96033f9 | | spark.sql.analyzer.unionIsResolvedWhenDuplicatesPerChildResolved | 4.1.0 | [SPARK-52686](https://issues.apache.org/jira/browse/SPARK-52686) | https://github.com/apache/spark/commit/308d3e899fd9271c98c7f815829c58a0ba35cd7b | | spark.sql.analyzer.uniqueNecessaryMetadataColumns | 4.1.0 | [SPARK-51544](https://issues.apache.org/jira/browse/SPARK-51544) | https://github.com/apache/spark/commit/aaa94c4e40dfe3dd4f7d05c2388903bad93a2907 | | spark.sql.parser.eagerEvalOfUnresolvedInlineTable | 4.0.0 | [SPARK-48967](https://issues.apache.org/jira/browse/SPARK-48967) | https://github.com/apache/spark/commit/b9b14f95c725c71670f0f9eda0c241de175f2b2d| | spark.sql.optimizer.datasourceV2JoinPushdown | 4.1.0 | [SPARK-52187](https://issues.apache.org/jira/browse/SPARK-52187) | https://github.com/apache/spark/commit/a66c74fd1d6f33d5c70a18e3bd2f47850717afdb| | spark.sql.optimizer.datasourceV2ExprFolding | 4.1.0 | [SPARK-53474](https://issues.apache.org/jira/browse/SPARK-53474) | https://github.com/apache/spark/commit/9d27db940673196f64b1568d73c459f83eb6f788| | spark.sql.streaming.stateStore.numStateStoreMaintenanceThreads | 4.1.0 | [SPARK-44480](https://issues.apache.org/jira/browse/SPARK-44480) | https://github.com/apache/spark/commit/9e42805f77c1ab5beb3c193f47f016e735a68f06| | spark.sql.streaming.stateStore.maintenanceShutdownTimeout | 4.1.0 | [SPARK-51397](https://issues.apache.org/jira/browse/SPARK-51397) | https://github.com/apache/spark/commit/7b1346b401d6769c9e2a8ad9262e39754fe1d132| | spark.sql.streaming.stateStore.maintenanceForceShutdownTimeout | 4.2.0 | [SPARK-54675](https://issues.apache.org/jira/browse/SPARK-54675) [SPARK-54655](https://issues.apache.org/jira/browse/SPARK-54655) | https://github.com/apache/spark/commit/6cec3c3647e2e11ad948621c8163270199309fb3| | spark.sql.streaming.stateStore.maintenanceProcessingTimeout | 4.1.0 | [SPARK-51596](https://issues.apache.org/jira/browse/SPARK-51596) | https://github.com/apache/spark/commit/51494a7f1216e56e0b88b00c42ec3f47f4343a45 | | spark.sql.streaming.internal.stateStore.partitions | 4.1.0 | [SPARK-53942](https://issues.apache.org/jira/browse/SPARK-53942) | https://github.com/apache/spark/commit/06674bab1db367fd9fb770fddc95b629f239291a | | spark.sql.streaming.metadataCache.enabled |3.4.0 | [SPARK-40957](https://issues.apache.org/jira/browse/SPARK-40957) | https://github.com/apache/spark/commit/5fa2c13cbf83c6c4c040f15bbbf66dbe49581bdc | | spark.sql.streaming.triggerAvailableNowWrapper.enabled | 4.1.0 | [SPARK-45178](https://issues.apache.org/jira/browse/SPARK-45178) | https://github.com/apache/spark/commit/227e262025229a67f43a8de452215053a9cbf662 | | spark.sql.optimizer.pullHintsIntoSubqueries |3.4.0| [SPARK-40999](https://issues.apache.org/jira/browse/SPARK-40999) | https://github.com/apache/spark/commit/0fa9c554fc0b3940a47c3d1c6a5a17ca9a8cee8e | ### Why are the changes needed? Supplemental configuration version information. ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? Exists UT ### Was this patch authored or co-authored using generative AI tooling? No -- 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]
