GitHub user yongtang opened a pull request:
https://github.com/apache/spark/pull/12305
[SPARK-14531][STREAMING] Flume streaming should respect maxRate
## What changes were proposed in this pull request?
At the moment Flume streaming set the default polling max batch size as
DEFAULT_POLLING_BATCH_SIZE (1000) even if an option
"spark.streaming.receiver.maxRate" is passed. This patch tries to address this
issue by respecting the option "spark.streaming.receiver.maxRate" in
FlumeUtils.scala.
## How was this patch tested?
A test case is added to cover the this change.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yongtang/spark SPARK-14531
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/12305.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 #12305
----
commit 7f6572ea530065b2777a96442c57f3029b66dfa1
Author: Yong Tang <yong.tang.git...@outlook.com>
Date: 2016-04-11T19:24:38Z
[SPARK-14531][STREAMING] Flume streaming should respect maxRate
At the moment Flume streaming set the default polling max batch size as
DEFAULT_POLLING_BATCH_SIZE (1000) even if an option
"spark.streaming.receiver.maxRate" is passed. This patch tries to address
this issue by respecting the option "spark.streaming.receiver.maxRate" in
FlumeUtils.scala.
A test case is added to cover the this change.
----
---
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
