You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2018/12/22 16:33:00 UTC
[jira] [Resolved] (SPARK-25245) Explain regarding limiting
modification on "spark.sql.shuffle.partitions" for structured streaming
[ https://issues.apache.org/jira/browse/SPARK-25245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen resolved SPARK-25245.
-------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Issue resolved by pull request 22238
[https://github.com/apache/spark/pull/22238]
> Explain regarding limiting modification on "spark.sql.shuffle.partitions" for structured streaming
> --------------------------------------------------------------------------------------------------
>
> Key: SPARK-25245
> URL: https://issues.apache.org/jira/browse/SPARK-25245
> Project: Spark
> Issue Type: Documentation
> Components: Structured Streaming
> Affects Versions: 2.4.0
> Reporter: Jungtaek Lim
> Assignee: Jungtaek Lim
> Priority: Major
> Fix For: 3.0.0
>
>
> Couple of users wondered why "spark.sql.shuffle.partitions" keeps unchanged when they changed the config value after running the query. Some of them even submitted the patch as this behavior as a bug. But it is based on how state is partitioned and the behavior is intentional.
> Looks like it's worth to explain it to guide doc so that no more users will be wondered.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org