You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (Jira)" <ji...@apache.org> on 2019/09/09 13:22:00 UTC

[jira] [Resolved] (SPARK-28939) SQL configuration are not always propagated

     [ https://issues.apache.org/jira/browse/SPARK-28939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wenchen Fan resolved SPARK-28939.
---------------------------------
    Fix Version/s: 3.0.0
       Resolution: Fixed

Issue resolved by pull request 25643
[https://github.com/apache/spark/pull/25643]

> SQL configuration are not always propagated
> -------------------------------------------
>
>                 Key: SPARK-28939
>                 URL: https://issues.apache.org/jira/browse/SPARK-28939
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 2.4.4
>            Reporter: Marco Gaido
>            Assignee: Marco Gaido
>            Priority: Major
>             Fix For: 3.0.0
>
>
> The SQL configurations are propagated to executors in order to be effective.
> Unfortunately, in some cases, we are missing to propagate them, making them un-effective.
> The problem happens every time {{rdd}} or {{queryExecution.toRdd}} are used. And this is pretty frequent in the codebase.
> Please notice that there are 2 parts of this issue:
>  - when a user directly uses those APIs
>  - when Spark invokes them (eg. throughout the ML lib and other usages or the {{describe}} method on the {{Dataset}} class)



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org