Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -1053,7 +1053,7 @@ object SQLConf {
.booleanConf
.createWithDefault(true)

val SUBQUERY_REUSE_ENABLED = buildConf("spark.sql.subquery.reuse")
val SUBQUERY_REUSE_ENABLED = buildConf("spark.sql.execution.subquery.reuse.enabled")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

now this is inconsistent with the exchange reuse: spark.sql.exchange.reuse

cc @rxin @maryannxue

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems we currently have the three patterns for boolean configs;

  • spark.sql.xxx.enabled, e.g., spark.sql.optimizer.dynamicPartitionPruning.enabled
  • spark.sql.enableXXX, e.g., spark.sql.inMemoryColumnarStorage.enableVectorizedReader
  • the names without enabled, e.g., spark.sql.exchange.reuse

We need a consistent rule for these boolean configs?

.internal()
.doc("When true, the planner will try to find out duplicated subqueries and re-use them.")
.booleanConf
Expand Down