Re: Exceed max.request.size of Kafka

Hi Jagadish， The 2 methods you provided I had tried already yesterday, then I found using the wrong Exception type, since I change to SamzaException it worked. Thanks for you help and explanation! QiShu > 在 2017年2月23日，23:47，Jagadish Venkatraman 写道： > > Hi

[GitHub] samza pull request #61: SAMZA-1103: ZkBarrier

GitHub user sborya opened a pull request: https://github.com/apache/samza/pull/61 SAMZA-1103: ZkBarrier SAMZA-1103: Barrier for JobModel upgrades. When all the processors got notification about the new JobModel, only after that they can start using the new model. You can merge

[GitHub] samza pull request #50: SAMZA-1102: Zk controller

Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/50 --- 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

[GitHub] samza pull request #58: SAMZA-1092: replace stream spec in fluent API

Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/58 --- 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

Re: Review Request 52168: Tasks endpoint to list the complete details of all tasks related to a job

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/52168/#review166245 --- First pass, will look at JobCoordinator changes separately.

Exceed max.request.size of Kafka

Hi, Sometimes there are huge size of data will occur in our flow, like 2MB, now samza will catch exception and shutdown like belowing.But what I want is I can handle such specific exception and just discard such data and the flow continues. 2017-02-23 16:17:01.949 [main]