Github user jnadler commented on the issue:
https://github.com/apache/spark/pull/15132
Not yet. Got Kafka 0.10 running and mirroring our production data streams
in prep for this test. I hope to get it tested next week.
On Thu, Oct 6, 2016 at 1:40 PM, Cody Koeninger
Github user jnadler commented on the issue:
https://github.com/apache/spark/pull/15132
Are you comfortable with the inconsistency this creates between Direct
Stream and Receivers? I don't need a receiver-based solution personally. It
does occur to me that it might be desirable
Github user jnadler commented on the issue:
https://github.com/apache/spark/pull/15132
Huge thank you to Cody Koeninger for working on this change. Looking
forward to 2.1.0.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user jnadler commented on the issue:
https://github.com/apache/spark/pull/15132
Building a test environment for this right now. Sorry for the delays.
---
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
Github user jnadler commented on the issue:
https://github.com/apache/spark/pull/15132
Testing has gone well. It's clearly successful in applying separate
maxrates to our 2 topics. Works as expected with backpressure enabled;
backpressure throttles both streams proportionally
Github user jnadler commented on the issue:
https://github.com/apache/spark/pull/15132
Just had first run that is basically working. The change to stop shading
Guava in Spark 2.x was a challenge. One thought, maybe PerPartitionConfig
should be Serializable. I had to add
Github user jnadler commented on the issue:
https://github.com/apache/spark/pull/15132
Anything I can do to help get the right person's attention?
---
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
