Github user gatorsmile commented on a diff in the pull request:

    https://github.com/apache/spark/pull/16826#discussion_r102140755
  
    --- Diff: 
sql/core/src/main/scala/org/apache/spark/sql/internal/SessionState.scala ---
    @@ -22,38 +22,58 @@ import java.io.File
     import org.apache.hadoop.conf.Configuration
     import org.apache.hadoop.fs.Path
     
    +import org.apache.spark.SparkContext
     import org.apache.spark.sql._
    -import org.apache.spark.sql.catalyst.TableIdentifier
     import org.apache.spark.sql.catalyst.analysis.{Analyzer, FunctionRegistry}
     import org.apache.spark.sql.catalyst.catalog._
     import org.apache.spark.sql.catalyst.optimizer.Optimizer
     import org.apache.spark.sql.catalyst.parser.ParserInterface
     import org.apache.spark.sql.catalyst.plans.logical.LogicalPlan
     import org.apache.spark.sql.execution._
    -import org.apache.spark.sql.execution.command.AnalyzeTableCommand
     import org.apache.spark.sql.execution.datasources._
    -import org.apache.spark.sql.streaming.{StreamingQuery, 
StreamingQueryManager}
    +import org.apache.spark.sql.streaming.StreamingQueryManager
     import org.apache.spark.sql.util.ExecutionListenerManager
     
     
     /**
      * A class that holds all session-specific state in a given 
[[SparkSession]].
      */
    -private[sql] class SessionState(sparkSession: SparkSession) {
    +private[sql] class SessionState(
    +    sparkContext: SparkContext,
    +    val conf: SQLConf,
    +    val experimentalMethods: ExperimentalMethods,
    +    val functionRegistry: FunctionRegistry,
    +    val catalog: SessionCatalog,
    +    val sqlParser: ParserInterface,
    +    val analyzer: Analyzer,
    +    val streamingQueryManager: StreamingQueryManager,
    +    val queryExecutionCreator: LogicalPlan => QueryExecution,
    +    val jarClassLoader: NonClosableMutableURLClassLoader) {
    --- End diff --
    
    `jarClassLoader ` is from SharedState. Do we still need it as an input parm 
for SessionState?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to