-
Notifications
You must be signed in to change notification settings - Fork 29.3k
[SPARK-28939][SQL][2.4] Propagate SQLConf for plans executed by toRdd #25734
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 3 commits
e9d22e1
d145b14
43bd021
a5eb604
1b145e2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -7,6 +7,12 @@ displayTitle: Spark SQL Upgrading Guide | |
| * Table of contents | ||
| {:toc} | ||
|
|
||
| ## Upgrading from Spark SQL 2.4 to 2.4.5 | ||
|
|
||
| - Starting from 2.4.5, SQL configurations are effective also when a Dataset is converted to an RDD and its | ||
| plan is executed due to action on the derived RDD. The previous buggy behavior can be restored setting | ||
| `spark.sql.legacy.rdd.applyConf` to `false`. | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hi, @hvanhovell , @cloud-fan and @gatorsmile . As @mgaido91 asked here, this PR will add this flag only at For me, we don't need to add this configuration to
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't think we need to add the flag to master. We are allowed to break behavior there. |
||
|
|
||
| ## Upgrading from Spark SQL 2.4 to 2.4.1 | ||
|
|
||
| - The value of `spark.executor.heartbeatInterval`, when specified without units like "30" rather than "30s", was | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -113,7 +113,9 @@ object SQLConf { | |
| * Returns the active config object within the current scope. If there is an active SparkSession, | ||
| * the proper SQLConf associated with the thread's active session is used. If it's called from | ||
| * tasks in the executor side, a SQLConf will be created from job local properties, which are set | ||
| * and propagated from the driver side. | ||
| * and propagated from the driver side, unless a `SQLConf` has been set in the scope by | ||
| * `withExistingConf` as done for propagating SQLConf for operations performed on RDDs created | ||
| * from DataFrames. | ||
| * | ||
| * The way this works is a little bit convoluted, due to the fact that config was added initially | ||
| * only for physical plans (and as a result not in sql/catalyst module). | ||
|
|
@@ -127,7 +129,12 @@ object SQLConf { | |
| */ | ||
| def get: SQLConf = { | ||
| if (TaskContext.get != null) { | ||
| new ReadOnlySQLConf(TaskContext.get()) | ||
| val conf = existingConf.get() | ||
| if (conf != null) { | ||
| conf | ||
| } else { | ||
| new ReadOnlySQLConf(TaskContext.get()) | ||
| } | ||
| } else { | ||
| val isSchedulerEventLoopThread = SparkContext.getActive | ||
| .map(_.dagScheduler.eventProcessLoop.eventThread) | ||
|
|
@@ -1291,6 +1298,14 @@ object SQLConf { | |
| .booleanConf | ||
| .createWithDefault(true) | ||
|
|
||
| val USE_CONF_ON_RDD_OPERATION = | ||
| buildConf("spark.sql.legacy.rdd.applyConf") | ||
| .internal() | ||
| .doc("When false, SQL configurations are disregarded when operations on a RDD derived from" + | ||
| " a dataframe are executed. This is the (buggy) behavior up to 2.4.3.") | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||
| .booleanConf | ||
| .createWithDefault(true) | ||
|
|
||
| val REPLACE_EXCEPT_WITH_FILTER = buildConf("spark.sql.optimizer.replaceExceptWithFilter") | ||
| .internal() | ||
| .doc("When true, the apply function of the rule verifies whether the right node of the" + | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,58 @@ | ||
| /* | ||
| * Licensed to the Apache Software Foundation (ASF) under one or more | ||
| * contributor license agreements. See the NOTICE file distributed with | ||
| * this work for additional information regarding copyright ownership. | ||
| * The ASF licenses this file to You under the Apache License, Version 2.0 | ||
| * (the "License"); you may not use this file except in compliance with | ||
| * the License. You may obtain a copy of the License at | ||
| * | ||
| * http://www.apache.org/licenses/LICENSE-2.0 | ||
| * | ||
| * Unless required by applicable law or agreed to in writing, software | ||
| * distributed under the License is distributed on an "AS IS" BASIS, | ||
| * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
| * See the License for the specific language governing permissions and | ||
| * limitations under the License. | ||
| */ | ||
| package org.apache.spark.sql.execution | ||
|
|
||
| import org.apache.spark.{Partition, TaskContext} | ||
| import org.apache.spark.rdd.RDD | ||
| import org.apache.spark.sql.catalyst.InternalRow | ||
| import org.apache.spark.sql.internal.SQLConf | ||
|
|
||
| /** | ||
| * It is just a wrapper over `sqlRDD`, which sets and makes effective all the configs from the | ||
| * captured `SQLConf`. | ||
| * Please notice that this means we may miss configurations set after the creation of this RDD and | ||
| * before its execution. | ||
| * | ||
| * @param sqlRDD the `RDD` generated by the SQL plan | ||
| * @param conf the `SQLConf` to apply to the execution of the SQL plan | ||
| */ | ||
| class SQLExecutionRDD( | ||
| var sqlRDD: RDD[InternalRow], conf: SQLConf) extends RDD[InternalRow](sqlRDD) { | ||
| private val sqlConfigs = conf.getAllConfs | ||
| private lazy val sqlConfExecutorSide = { | ||
|
dongjoon-hyun marked this conversation as resolved.
|
||
| val newConf = new SQLConf() | ||
| sqlConfigs.foreach { case (k, v) => newConf.setConfString(k, v) } | ||
| newConf | ||
| } | ||
|
|
||
| override val partitioner = firstParent[InternalRow].partitioner | ||
|
|
||
| override def getPartitions: Array[Partition] = firstParent[InternalRow].partitions | ||
|
|
||
| override def compute(split: Partition, context: TaskContext): Iterator[InternalRow] = { | ||
| // If we are in the context of a tracked SQL operation, `SQLExecution.EXECUTION_ID_KEY` is set | ||
| // and we have nothing to do here. Otherwise, we use the `SQLConf` captured at the creation of | ||
| // this RDD. | ||
| if (context.getLocalProperty(SQLExecution.EXECUTION_ID_KEY) == null) { | ||
| SQLConf.withExistingConf(sqlConfExecutorSide) { | ||
| firstParent[InternalRow].iterator(split, context) | ||
| } | ||
| } else { | ||
| firstParent[InternalRow].iterator(split, context) | ||
| } | ||
| } | ||
| } | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd personally refrain from using the term
buggy. Please explain what the previous behavior was.