You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Tathagata Das (JIRA)" <ji...@apache.org> on 2017/03/17 23:15:41 UTC
[jira] [Resolved] (SPARK-19873) If the user changes the number of
shuffle partitions between batches, Streaming aggregation will fail.
[ https://issues.apache.org/jira/browse/SPARK-19873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tathagata Das resolved SPARK-19873.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.2.0
Issue resolved by pull request 17216
[https://github.com/apache/spark/pull/17216]
> If the user changes the number of shuffle partitions between batches, Streaming aggregation will fail.
> ------------------------------------------------------------------------------------------------------
>
> Key: SPARK-19873
> URL: https://issues.apache.org/jira/browse/SPARK-19873
> Project: Spark
> Issue Type: Bug
> Components: Structured Streaming
> Affects Versions: 2.1.0
> Reporter: Kunal Khamar
> Fix For: 2.2.0
>
>
> If the user changes the shuffle partition number between batches, Streaming aggregation will fail.
> Here are some possible cases:
> - Change "spark.sql.shuffle.partitions"
> - Use "repartition" and change the partition number in codes
> - RangePartitioner doesn't generate deterministic partitions. Right now it's safe as we disallow sort before aggregation. Not sure if we will add some operators using RangePartitioner in future.
> Fix:
> Record # shuffle partitions in offset log and enforce in next batch
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org