Missing artifact? org.apache.samza:samza-serializers_2.10:jar:0.9.0

Hi all, I was following the instructions (http://samza.apache.org/startup/download/ ) to upgrade to Samza 0.9.0 but ran into a maven build failure - "Failure to find org.apache.samza:samza-serializers_2.10:jar:0.9.0”. Looking in the Apache Maven repos

Re: Review Request 35241: refactoring the code for coordinator stream writer

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35241/ --- (Updated June 9, 2015, 11:53 p.m.) Review request for samza, Yi Pan (Data Infra

Re: Review Request 35241: refactoring the code for coordinator stream writer

> On June 9, 2015, 11:03 p.m., Yan Fang wrote: > > Which JIRA is this one related? This is related to the SAMZA-704 JIRA - Shadi --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35241/#review8

Re: Review Request 35115: SAMZA-474 check-all script should fail more gracefully in the absence of gradlew

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35115/#review87312 --- bin/check-all.sh

Re: Review Request 35241: refactoring the code for coordinator stream writer

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35241/#review87309 --- Which JIRA is this one related? - Yan Fang On June 9, 2015, 1:58

Re: Samza Consumer / Producer Question

Hi Chas, In terms of the consumer, you can also refer to the Kafka Consumer , which will give you another view of how to implement the consumer. But I am very curious, w

Re: Issues with certain characters in config values

Hi Navina, Yes, I'm seeing the issue on 0.8.0. As I mentioned in the bug, I know the method of passing the config is changing, but I still wanted to get the issue on record. With regard to Util.envVarEscape(), the assumption seems to be that the value is going through the shell at some point,

Re: Issues with certain characters in config values

Hi Tommy, I wouldn't think Util.envVarEscape() is totally unnecessary. Are you running into this issue with a version <= 0.9 ? With 0.10, I think we no longer pass all the environment variables through command line. We only pass the Coordinator system information via command line. While Util.env

Re: Memory issue

Hi Yan, that worked thanks! Davide > On 6 Jun 2015, at 12:42 am, Yan Fang wrote: > > Hi Davide, > > Consumer takes the memory is because it maintains a cache for the messages, > the size by default is 5. In your case, it maybe as big as 5*12kb. > See systems.system-name. > samza.fe

Re: Issues with certain characters in config values

Ok, the issue with spaces appears to have been addressed by https://issues.apache.org/jira/browse/SAMZA-530. But quotes are still a problem, and I'm becoming increasingly convinced that Util.envVarEscape() method is unnecessary. On 06/08/2015 03:02 PM, Tommy Becker wrote: We have a stream job

Re: Review Request 33297: [SAMZA-654] Added ElasticsearchSystemProducer and Factory to output messages into Elasticseach indexes.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/33297/ --- (Updated June 9, 2015, 11:42 a.m.) Review request for samza. Repository: samz

Re: Review Request 33297: [SAMZA-654] Added ElasticsearchSystemProducer and Factory to output messages into Elasticseach indexes.

> On May 4, 2015, 6:53 a.m., Yan Fang wrote: > > samza-elasticsearch/src/main/java/org/apache/samza/config/ElasticsearchConfig.java, > > lines 93-110 > > > > > > those are general methods. I think there are two ways