Re: Review Request 44920: SAMZA-680 Refactor the Samza AppMaster to support other cluster managers

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/44920/ --- (Updated May 10, 2016, 11:50 p.m.) Review request for samza, Boris Shkolnik,

Review Request 47197: SAMZA-948 CoordinatorSystemStreamConsumer is not threadsafe

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/47197/ --- Review request for samza, Boris Shkolnik, Chris Pettitt, Jake Maes, Navina

Re: Kafka dependency

Hi, Nick, Good point. Sorry I forgot to push the latest tag out to the remote repo. Here is the tag that used to publish all binary tar balls: release-0.10.0-rc2 Thanks! -Yi On Tue, May 10, 2016 at 11:24 AM, Nick Quinn wrote: > Thanks Yi! > > One more question, if I

Re: Kafka dependency

Just want to chime in to add we'd like to use some of the new security features in Kafka 0.9, ACLs and TLS in particular. On Tue, May 10, 2016 at 11:24 AM, Nick Quinn wrote: > Thanks Yi! > > One more question, if I may: I saw that you dropped a 0.10.0 in December > of

RE: Kafka dependency

Thanks Yi! One more question, if I may: I saw that you dropped a 0.10.0 in December of 2015, but the version in Github is still 0.10.0-rc. Do you guys plan on an official release of 0.10.0 or are you settling for a simple rc release? The reason I ask is that it is hard to match the git

Re: Kafka dependency

Hi, Nick, We do have plan to update the Kafka dependency in Samza. However, Samza only uses Kafka client library. We have confirmed that any Kafka 0.8.2 clients should be supported by Kafka 0.9 brokers. Hence, it should not block you if you are thinking of upgrading Kafka broker versions (e.g.

Kafka dependency

Hi guys- I was wondering why Samza still has a dependency on Kafka 0.8.2. Does your development team have any plans to update the Kafka dependency version that Samza is using? Best, Nick

Re: Howto Use The Elasticsearch Producer

Glad to hear it! I'll add a JIRA task to always log the exception. We shouldn't need to enable debug logging to fix issues like this. On Tue, May 10, 2016 at 10:16 AM, Tim Washington < tim.washing...@fundingcircle.com> wrote: > Hey Jacob, right you are. > > I added a "**" > logback

Re: Howto Use The Elasticsearch Producer

Hey Jacob, right you are. I added a "**" logback configuration. And lo and behold, this exception detail popped up. 10:05:47.520 [main] DEBUG o.a.samza.container.SamzaContainer$ - Exception detail: java.lang.RuntimeException: Could not instantiate class

Re: Review Request 46287: Add a double serde.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/46287/#review132481 --- Ship it! +1. lgtm! - Yi Pan (Data Infrastructure) On April

Re: Howto Use The Elasticsearch Producer

Hey Tim, Can you include the full log? Since the producer is not showing up, I'd expect to see some earlier messages explaining why. In particular, this section of code from SamzaContainer.scala should print errors instantiating the producers: val producers = systemFactories > .map { >

Fwd: Howto Use The Elasticsearch Producer

*Tim Washington* | *Senior Software Engineer* *tim.washing...@fundingcircle.com * 747 Front St, 4th Fl | San Francisco, CA 94111 *Our Mission: **T**o build a better financial world* -- Forwarded message -- From: Tim Washington