[CANCEL][VOTE] SEP-11: Host affinity in standalone.

Hi, This is an official CANCEL for the SEP-11: Host affinity in standalone vote. Thanks.

[GitHub] samza pull request #444: SAMZA-1615: Fix a couple of issues in ControlMessag...

Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/444 ---

RE: Old style "low level" Tasks with alternative deployment model(s)

Thanks a lot for the info. I have something basically working at this point! I have not integrated it with Docker nor Kubernetes yet, but it does run from my local machine. I have determined that LocalApplicationRunner does NOT do config rewriting. I had to write my own little

Re: Old style "low level" Tasks with alternative deployment model(s)

>> Thanks for the info on the tradeoffs. That makes a lot of sense. I am on-board with using ZkJobCoordinator, sounds like some good benefits over just the Kafka high-level consumer. This certainly looks like the simplest alternative. For your other questions, please find my answers inline. >>

Re: Streams Meetup at LinkedIn Sunnyvale 3/21/2018

Hey folks, We have an exciting line-up of tech-talks on use-cases for Apache Samza and Kafka! A friendly reminder to RSVP at https://www.meetup.com/Stream- Processing-Meetup-LinkedIn/events/248309045/ Best, Jagdish On Thu, Mar 1, 2018 at 3:16 PM, Jake Maes wrote: > Hi

RE: Old style "low level" Tasks with alternative deployment model(s)

Thanks for the info on the tradeoffs. That makes a lot of sense. I am on-board with using ZkJobCoordinator, sounds like some good benefits over just the Kafka high-level consumer. To that end, I have made some notes on possible approaches based on the previous thread, and from my look into

[GitHub] samza pull request #449: SAMZA-1622: avro writer to support generic record

GitHub user lhaiesp opened a pull request: https://github.com/apache/samza/pull/449 SAMZA-1622: avro writer to support generic record avro writer in HDFS system producer to support generic record You can merge this pull request into a Git repository by running: $ git pull

Re: Old style "low level" Tasks with alternative deployment model(s)

>> You are correct that this is focused on the higher-level API but doesn't preclude using the lower-level API. I was at the same point you were not long ago, in fact, and had a very productive conversation on the list Thanks Tom for linking the thread, and I'm glad that you were able to get