Supported Kafka version by Samza

Hi, Running environment: Samza version: 2.12-1.1.0 Kafka cluster version: 2.12-1.1.0 Hadoop version: 3.1.0 When using Kafka_2.12-1.1.0.jar, Samza job failed to run when retrieving coordinator stream meta info from Kafka: 2019-06-03 17:26:11.176 [main] KafkaSystemAdmin [INFO] Fetc

Re: REMINDER. [VOTE] Apache Samza 1.2.0 RC4

+1 (non-binding) Verified build and test on Linux box. On mac the test is failing but seems like flakiness not real failure. Thanks, Hai On Tue, Jun 4, 2019 at 1:55 PM santhosh venkat wrote: > +1(non-binding) > > 1. ./bin/check-all.sh succeeded > 2. ./bin/integration-tests.sh succeeded > 3. Ex

Re: REMINDER. [VOTE] Apache Samza 1.2.0 RC4

+1(non-binding) 1. ./bin/check-all.sh succeeded 2. ./bin/integration-tests.sh succeeded 3. Expanded samza-tools and followed the tutorial steps for standalone SQL examples Succeeded. 4. Verified all sha1 hash code and asc signatures successfully Thanks, On Tue, Jun 4, 2019 at 1:26 PM Xinyu Liu

Re: REMINDER. [VOTE] Apache Samza 1.2.0 RC4

+1 (binding). run check-all.sh and the build passed. Having trouble running the integration tests in both linux and mac, possibly due to my local machine env. Thanks, Xinyu On Mon, Jun 3, 2019 at 11:00 AM Daniel Nishimura wrote: > check-all.sh and integration tests passed. +1 from me. > > Jus

Re: Supported Versions Question

Hi Darin, The recommended dependency version in release notes are the ones we validate our releases. Typically, the patch and minor versions of the recommended dependency version works. Here is the supported matrix for Kafka clients Dependency Supported versions Not supported version Samza versi

Re: Limiting the job coordinator port range

Hi Malcolm, The JC server is currently started on a random port. This is because multiple JCs can exist on the same host, so using a framework-wide pre-defined port causes bind conflicts. There's currently no way to narrow down the range or fix the port on a per-job basis. If you want to add a con

Limiting the job coordinator port range

Hey folks, Is there any way to specify which ports the tasks communicate with the job coordinator on? Right now it looks like it's 3+. Is there any way to narrow this? Cheers, Malcolm McFarland Cavulus This correspondence is from HealthPlanCRM, LLC, d/b/a Cavulus. Any unauthorized or improp