You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sanford Ryza (Jira)" <ji...@apache.org> on 2025/11/12 00:24:00 UTC

[jira] [Updated] (SPARK-53995) Add support to track `spark_conf` at the dataset level

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

Sanford Ryza updated SPARK-53995:
---------------------------------
        Parent:     (was: SPARK-51727)
    Issue Type: Improvement  (was: Sub-task)

> Add support to track `spark_conf` at the dataset level
> ------------------------------------------------------
>
>                 Key: SPARK-53995
>                 URL: https://issues.apache.org/jira/browse/SPARK-53995
>             Project: Spark
>          Issue Type: Improvement
>          Components: Declarative Pipelines
>    Affects Versions: 4.1.0
>            Reporter: Yuheng Chang
>            Priority: Major
>
> We need to add {{sql_confs}} to {{DefineOutput}} in SDP to support following use case
> SQL file #1
> {code:java}
> SET some_conf = some_value;
> CREATE STREAMING TABLE st; {code}
> SQL file #2
> CREATE FLOW INSERT INTO st FROM ....
>  
> Since we don't store {{sql_confs}} at the Dataset level, the conf would be ignored. We should store it at dataset level and will merge the {{sql_conf}} stored at the dataset level to its corresponding flow when we construct the DataflowGraph.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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