GitHub user kunalkhamar opened a pull request:
https://github.com/apache/spark/pull/17216
[SPARK-19873][SS] Record num shuffle partitions in offset log and enforce
in next batch.
## What changes were proposed in this pull request?
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.
## How was this patch tested?
Unit tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kunalkhamar/spark num-partitions
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/17216.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #17216
----
commit 12f5fd30229e441355a05290ed124263c1429acc
Author: Kunal Khamar <kkha...@outlook.com>
Date: 2017-03-08T21:29:02Z
Record num shuffle partitions in offset log and enforce in next batch.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
