Re: [DISCUSS] SQL workflow

the revision changes in a dependency chain. Cheers, Chris On Thu, Feb 5, 2015 at 12:16 PM, Jakob Homan jgho...@gmail.com wrote: I want to avoid branches, Just curious, any reason for this? and I also want to avoid revision control over JIRA Eh? Not sure what this means

Re: [DISCUSS] SQL workflow

/discarded? RB is not designed to track the revision changes in a dependency chain. Cheers, Chris On Thu, Feb 5, 2015 at 12:16 PM, Jakob Homan jgho...@gmail.com wrote: I want to avoid branches, Just curious, any reason for this? and I also want

Re: Running Samza on Windows

We've not yet had anyone running Samza on Windows, though there should be nothing in the code to prevent this. There are no dos/powershell batch scripts, so you'd need cygwin (or a wrapper like mobaxterm). Patches to add this support directly would be welcome. -jakob On 13 February 2015 at

Re: [VOTE] Apache Samza 0.9.0 RC0

-loss/correctness issues in Samza, but I just want to make sure. Planning to run the burn-in over the weekend. I'll open up JIRAs to fix the SAMZA-394 torture tests once I'm confident it's stable. Cheers, Chris On Fri, Mar 27, 2015 at 4:28 PM, Jakob Homan jgho...@gmail.com wrote

Re: [VOTE] Apache Samza 0.9.0 RC0

a join * Build packages * Couldn't get integration tests to work. It seemed like it was timing out trying to download dependencies. I may have been having network issues last night. Cheers, Roger On Sun, Mar 29, 2015 at 9:09 PM, Jakob Homan jgho...@gmail.com

Re: Questions about partitioning

Hey Susan- That volume of topics (or partitions) would be a significant burden on both the Kafka cluster and underlying YARN cluster (for the Samza job). A 'large number of partitions' even at places with huge Kafka clusters is on the order of 512 or so. It sounds like you're trying to use

Re: Review Request 33305: [SAMZA-655] Add EnvironmentConfigRewriter to samza-api.

/samza/config/EnvironmentConfigRewriterTest.java https://reviews.apache.org/r/33305/#comment130508 Need ASF header - Jakob Homan On April 17, 2015, 6:12 a.m., Dan Harvey wrote: --- This is an automatically generated e-mail. To reply

Re: Extra Systems and other extensions.

Hey Dan- I'd love for the Elastic Search stuff to be added to the main code, as a separate module. Keeping these in the main source code keeps them more likely to be maintained and correct. The EvironemtnConfigRewriter can likely go in the same place as the ConfigRewriter interface, since it

Re: New user here

Yeah, this is fine. Incubator has a weird thing against running user lists during Incubation. Now that we've gone TLP, we should probably open an INFRA ticket to create a user list. -jakob On 8 April 2015 at 12:20, jeremy p athomewithagroove...@gmail.com wrote: Hello all, I am new to Samza.

[CANCEL][VOTE] Apache Samza 0.9.1 RC0

As discussed, this vote has been CANCELED. On 25 June 2015 at 16:34, Yan Fang yanfang...@gmail.com wrote: no objection from me. :) Thanks, Fang, Yan yanfang...@gmail.com On Thu, Jun 25, 2015 at 4:18 PM, Yi Pan nickpa...@gmail.com wrote: Hi, all, I have been preparing for the new 0.9.1

Re: [VOTE] Apache Samza 0.9.1 RC1

s/test-patch/check-all/ Guess which project I've been working on? On 1 July 2015 at 21:22, Jakob Homan jgho...@gmail.com wrote: +1 (binding). Artifacts are good, tests pass, code looks good. Found minor issue with test-patch (SAMZA-726), but doesn't affect release. It's pretty standard

Re: Do we want to release the 0.9.1 now?

- SAMZA-655: Add environment variable configuration rewriter. (4 weeks ago) Dan Harvey * 5a035b8 - Update committer list (5 weeks ago) Yi Pan (Data Infrastructure) * a09b1ff - SAMZA-646: Remove support for JDK6 (5 weeks ago) Jakob Homan * ffa84c0 - SAMZA-608; don't hange on serde errors in system

Re: Thoughts and obesrvations on Samza

I'm afraid I don't agree that we're anywhere near coming to a consensus, or even that we're all agreeing on what we're discussing. (I do totally agree that the discussion itself has been awesome both in tone and content, though). As Tim brought up and I mentioned, the Board is not big on

Re: Thoughts and obesrvations on Samza

This leads me to thinking that merging projects and communities might be a good idea: with the union of experience from both communities, we will probably build a better system that is better for users. Is this what's being proposed though? Merging the projects seems like a consequence of at

Re: Hello Samza repository + Data Masking

The big hurdle here is that Hello Samza (HS) should always be ready to go and work right out of the box, whereas a fresh checkout of trunk may (though hopefully doesn't) have issues. This is why HS by default points to the last stable Samza release (and has to be re-branched to track master on

Re: Executing Samza jobs natively in Kubernetes

Hey Elias- This is awesome work. Would be interested in opening JIRAs for the changes you need so we can start to process them? Thanks, Jakob On 30 November 2015 at 12:18, Roger Hoover wrote: > Awesome. Thanks. > > On Sun, Nov 29, 2015 at 3:25 PM, Elias Levy

Re: [DISCUSS] [VOTE] Apache Samza 0.11.0 RC0

+1 binding. Verified MD5, checked code, built and tested. Good job, everyone. -Jakob On 4 October 2016 at 09:23, Jacob Maes wrote: > +1 (non-binding) > > Downloaded and bin/check-all.sh on OSX > Downloaded, built and ran unit tests on RHEL > > I got a checkstyle error

Re: [VOTE] Apache Samza 0.11.0 RC2

+1 (binding) Ran tests, verified sig and md5. Looks good. -Jakob btw, were [CANCEL] emails sent out for the other RC votes? I don't see any. Is a good idea to do so. On 13 October 2016 at 09:54, Jagadish Venkatraman wrote: > +1 (non binding) > > On Wed, Oct 12, 2016

[ANNOUNCE] Please welcome Boris Shkolnik to the Samza PMC

Howdy all- I'm very pleased to announce that the Samza PMC has voted Boris Shkolnik to be a Project Management Committee (PMC) Member. The PMC is responsible for the overall health of a project andl for voting in new committers and PMC members, as well as VOTEing on releases. Over the past two