[
https://issues.apache.org/jira/browse/SPARK-26493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyukjin Kwon resolved SPARK-26493.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Issue resolved by pull request 23398
[https://github.com/apache/spark/pull/23398]
> spark.sql.extensions should support multiple extensions
> -------------------------------------------------------
>
> Key: SPARK-26493
> URL: https://issues.apache.org/jira/browse/SPARK-26493
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Jamison Bennett
> Assignee: Jamison Bennett
> Priority: Minor
> Labels: starter
> Fix For: 3.0.0
>
>
> The spark.sql.extensions configuration options should support multiple
> extensions. It is currently possible to load multiple extensions using the
> programatic interface (e.g.
> SparkSession.builder().master("..").withExtensions(sparkSessionExtensions1).withExtensions(sparkSessionExtensions2).getOrCreate()
> ) but the same cannot currently be done with the command line options
> without writing a wrapper extensions that combines multiple extensions.
>
> Allowing multiple spark.sql.extensions, would allow the extensions to be
> easily changes on the command line or via the configuration file. Multiple
> extensions could be specified using a comma separated list of class names.
> Allowing multiple extensions should maintain backwards compatibility because
> existing spark.sql.extensions configuration settings shouldn't contain a
> comma because the value is a class name.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
