Re: [DISCUSS] Samza 0.13.0 release

2017-05-08 Thread Jagadish Venkatraman
0.13 has some exciting new features like - Fluent API and Samza stand-alone. The plan looks great to me, +1. If there are no more new request for changes, let us target getting an RC out sometime mid of this week. Thanks again for driving the release!! Best, Jagadish On Mon, May 8, 2017 at 1:56

[GitHub] samza pull request #169: SAMZA-1268: Javadoc cleanup for public APIs for 0.1...

2017-05-08 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/169 --- 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 enabl

[GitHub] samza pull request #173: SAMZA-1272 : ZkCoordinationUtils deletes the entire...

2017-05-08 Thread navina
GitHub user navina opened a pull request: https://github.com/apache/samza/pull/173 SAMZA-1272 : ZkCoordinationUtils deletes the entire Zk tree on reset * ZkCoordinationUtils has a reset interface that deletes the entire Zk tree. This is not desirable. * Also, fixed flakiness in

[GitHub] samza pull request #166: SAMZA-1150 : Handling Error propagation between ZkJ...

2017-05-08 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/166 --- 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 enabl

[GitHub] samza pull request #172: SAMZA-1273: Make StreamConfig.getStreamIds() public

2017-05-08 Thread xinyuiscool
GitHub user xinyuiscool opened a pull request: https://github.com/apache/samza/pull/172 SAMZA-1273: Make StreamConfig.getStreamIds() public Making StreamConfig.getStreamIds() public so config provider can scan through all the configured streams and expand some properties if needed.

[GitHub] samza pull request #164: SAMZA-1206: Fix TestJMXServer.

2017-05-08 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/164 --- 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 enabl

[GitHub] samza pull request #140: SAMZA-1196: Fix TestJmxReporter

2017-05-08 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/140 --- 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 enabl

[GitHub] samza pull request #137: SAMZA-1232: Log configuration value in RunLoopFacto...

2017-05-08 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/137 --- 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 enabl

Re: [DISCUSS] Samza 0.13.0 release

2017-05-08 Thread Jacob Maes
+1 on the release. The plan looks good. It goes without saying that documentation is also required. SAMZA-1234 is the umbrella ticket for that. On Fri, May 5, 2017 at 4:42 PM, Prateek Maheshwari < pmaheshw...@linkedin.com.invalid> wrote: > Hi all, > > There have been quite a lot of new features

[GitHub] samza pull request #171: Disabled a few flaky tests and added corresponding ...

2017-05-08 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/171 --- 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 enabl

[GitHub] samza pull request #171: Disabled a few flaky tests and added corresponding ...

2017-05-08 Thread prateekm
GitHub user prateekm opened a pull request: https://github.com/apache/samza/pull/171 Disabled a few flaky tests and added corresponding tickets to fix. You can merge this pull request into a Git repository by running: $ git pull https://github.com/prateekm/samza disable-flaky-

[GitHub] samza pull request #170: Disabled a few flaky tests and added corresponding ...

2017-05-08 Thread prateekm
Github user prateekm closed the pull request at: https://github.com/apache/samza/pull/170 --- 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 ena

[GitHub] samza pull request #170: Disabled flaky test TestProcessJob testProcessJobKi...

2017-05-08 Thread prateekm
GitHub user prateekm opened a pull request: https://github.com/apache/samza/pull/170 Disabled flaky test TestProcessJob testProcessJobKillShouldWork To be fixed in SAMZA-1261 You can merge this pull request into a Git repository by running: $ git pull https://github.com/prateek

[GitHub] samza pull request #169: SAMZA-1268: Javadoc cleanup for public APIs for 0.1...

2017-05-08 Thread prateekm
GitHub user prateekm opened a pull request: https://github.com/apache/samza/pull/169 SAMZA-1268: Javadoc cleanup for public APIs for 0.13 release You can merge this pull request into a Git repository by running: $ git pull https://github.com/prateekm/samza api-docs-cleanup Al

Re: Possible bug causing reset in offsets [Version: 0.12.0].

2017-05-08 Thread Jagadish Venkatraman
Hi Gaurav (and others in this thread), My apologies for the late reply, This e-mail appears to have missed my inbox somehow. >From your logs, It appears that there was a leadership change happening on the Kafka side for this topic partition? If so, I would actually expect the follower's offset to

[GitHub] samza pull request #168: SAMZA-1267: ApplicationRunner#getLocalRunner return...

2017-05-08 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/168 --- 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 enabl

Stream Processing Meetup on May 24th at LinkedIn Sunnyvale

2017-05-08 Thread Jake Maes
Hey Folks, We wanted to invite you to the upcoming Stream Processing meetup at the Linkedin Sunnyvale HQ. The meetup is on Wednesday May 24 from 6-9PM. We'll have food and refreshments as usual, but more importantly we have 3 exciting talks planned. - Streaming Data Pipelines with Brooklin