[GitHub] samza pull request #91: SAMZA-1151. Coordination service.

2017-03-17 Thread sborya
GitHub user sborya opened a pull request: https://github.com/apache/samza/pull/91 SAMZA-1151. Coordination service. You can merge this pull request into a Git repository by running: $ git pull https://github.com/navina/samza CoordinationService Alternatively you can review an

[GitHub] samza pull request #70: SAMZA-1115:Job coordinator

2017-03-17 Thread sborya
Github user sborya closed the pull request at: https://github.com/apache/samza/pull/70 --- 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 enable

[GitHub] samza pull request #87: SAMZA-1146: TaskCallbackManager commit fix.

2017-03-17 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/87 --- 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 enable

[GitHub] samza pull request #85: SAMZA-1140 : Non blocking commit in Async Runloop

2017-03-17 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/85 --- 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 enable

[GitHub] samza pull request #88: SAMZA-1131: RemoteApplicationRunner for cluster-base...

2017-03-17 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/88 --- 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 enable

[DISCUSS] Support Scala 2.12

2017-03-17 Thread Maksim Logvinenko
Hi guys, I’ve created JIRA and already submitted patch which adds support of scala 2.12. Here is the ticket: https://issues.apache.org/jira/browse/SAMZA-1135. Nothing serious: I’ve removed JavaConversions usage (because it’s marked as deprecated now) and bumped kafka and scalatest versions since p

Re: [DISCUSS] Support Scala 2.12

2017-03-17 Thread Jagadish Venkatraman
Thanks for starting this discussion and the patch. +1 for supporting scala 2.12. I assume the changes are fully backwards compatible with scala 2.10, 2.11 (as evidenced by your check-all)? Also, another observation is that the generated Samza binaries will have 2.12 as the suffix for the future r

Re: [DISCUSS] Support Scala 2.12

2017-03-17 Thread Navina Ramesh
Thanks for creating the DISCUSS email! This is good. It's a good idea to update to 2.12 since it looks like we are fully backward compatible with older versions. +1 from me. Cheers! Navina On Fri, Mar 17, 2017 at 1:34 PM, Jagadish Venkatraman < jagadish1...@gmail.com> wrote: > Thanks for starti

[GitHub] samza pull request #92: SAMZA-1094, SAMZA-1101: Remove MessageEnvelope from ...

2017-03-17 Thread prateekm
GitHub user prateekm opened a pull request: https://github.com/apache/samza/pull/92 SAMZA-1094, SAMZA-1101: Remove MessageEnvelope from public operator APIs. Delay the creation of SinkFunction for output streams. Additionally, 1. Removed references to StreamGraph in OperatorSpec