From 71a29b2eca0b5f3c7bd51259796ca007774d8fd6 Mon Sep 17 00:00:00 2001 From: Max Gekk Date: Mon, 16 Nov 2020 17:57:20 +0900 Subject: [PATCH] [MINOR][SQL][DOCS] Fix a reference to `spark.sql.sources.useV1SourceList` ### What changes were proposed in this pull request? Replace `spark.sql.sources.write.useV1SourceList` by `spark.sql.sources.useV1SourceList` in the comment for `CatalogManager.v2SessionCatalog()`. ### Why are the changes needed? To have correct comments. ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? By running `./dev/scalastyle`. Closes #30385 from MaxGekk/fix-comment-useV1SourceList. Authored-by: Max Gekk Signed-off-by: HyukjinKwon --- .../org/apache/spark/sql/connector/catalog/CatalogManager.scala | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sql/catalyst/src/main/scala/org/apache/spark/sql/connector/catalog/CatalogManager.scala b/sql/catalyst/src/main/scala/org/apache/spark/sql/connector/catalog/CatalogManager.scala index 8e8cd786b7..fc2ab99a3d 100644 --- a/sql/catalyst/src/main/scala/org/apache/spark/sql/connector/catalog/CatalogManager.scala +++ b/sql/catalyst/src/main/scala/org/apache/spark/sql/connector/catalog/CatalogManager.scala @@ -78,7 +78,7 @@ class CatalogManager( * This catalog is a v2 catalog that delegates to the v1 session catalog. it is used when the * session catalog is responsible for an identifier, but the source requires the v2 catalog API. * This happens when the source implementation extends the v2 TableProvider API and is not listed - * in the fallback configuration, spark.sql.sources.write.useV1SourceList + * in the fallback configuration, spark.sql.sources.useV1SourceList */ private[sql] def v2SessionCatalog: CatalogPlugin = { conf.getConf(SQLConf.V2_SESSION_CATALOG_IMPLEMENTATION).map { _ =>