Re: Podling Report Reminder - November 2016

Hi guys @James do you want to prepare this podling report ? I will review. Let me know if you need any help. Thanks Regards JB ⁣​ On Oct 25, 2016, 02:02, at 02:02, johndam...@apache.org wrote: >Dear podling, > >This email was sent by an automated system on behalf of the Apache >Incubator PMC.

Re: [DISCUSS] Using Verbs for Transforms

Sounds good to me. ⁣​ On Oct 24, 2016, 19:11, at 19:11, je...@smokinghand.com wrote: >I prefer MakeDistinct if we have to make it a verb.

Re: [DISCUSS] Current ongoing work on runners

I think it would be worth publishing a compatibility matrix, if not on the main site, as part of the branch itself. Even better would be if the compatibility matrix was automatically deduced based on a suite of tests that each runner could (attempt to) pass. On Mon, Oct 24, 2016 at 12:52 PM,

Re: [DISCUSS] Using Verbs for Transforms

On Mon, Oct 24, 2016 at 10:12 AM, Kenneth Knowles wrote: > The precedent that we use verbs has many exceptions. We have > ApproximateQuantiles, Values, Keys, WithTimestamps, and I would even > include Sum (at least when I read it). True. > Historical note: the

Podling Report Reminder - November 2016

Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 16 November 2016, 10:30 am PDT. The report for your podling will

The Availability of PipelineOptions

Hey everyone, I've been working on a declaration of intent for how we want to use PipelineOptions and an API change to be consistent with that intent. This is generally part of the move to the Runner API, specifically the desire to be able to reuse Pipelines and the ability to choose runner at

Re: [DISCUSS] Using Verbs for Transforms

That's how the mainframe programmers I've dealt with refer to it. I agree with Dan. We should either not change the name or change it to Distinct. It's just not worth the effort otherwise. On Mon, Oct 24, 2016, 3:10 PM Eugene Kirpichov wrote: > $0.02: Deduplicate?

Re: [DISCUSS] Using Verbs for Transforms

$0.02: Deduplicate? (lends to extensions like Deduplicate.by(some key extractor function)) On Mon, Oct 24, 2016 at 1:22 PM Dan Halperin wrote: > I find "MakeDistinct" more confusing. My votes in decreasing preference: > > 1. Keep `RemoveDuplicates` name, ensure that

[VOTE] Release 0.3.0-incubating, release candidate #1

Hi Team! Please review and vote at your leisure on release candidate #1 for version 0.3.0-incubating, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) The complete staging area is available for your review, which includes: * JIRA

Re: Tracking backward-incompatible changes for Beam

I don't think we have it right now. We should, of course, but this is something that needs to be defined/discussed first. On Mon, Oct 24, 2016 at 1:20 PM, Neelesh Salian wrote: > +1 for the labels and also a need for tests. > Do we document any rules for

Re: [DISCUSS] Using Verbs for Transforms

I find "MakeDistinct" more confusing. My votes in decreasing preference: 1. Keep `RemoveDuplicates` name, ensure that important keywords are in the Javadoc. This reduces churn on our users and is honestly pretty dang descriptive. 2. Rename to `Distinct`, which is clear if you're a SQL user and

Re: Tracking backward-incompatible changes for Beam

+1 for the labels and also a need for tests. Do we document any rules for backward-compatibility? Be good to have a checklist-like list. On Mon, Oct 24, 2016 at 1:02 PM, Davor Bonaci wrote: > It would be awesome to have that! At least a good portion of >

Re: Maven Release Plugin Does Not Update Version of Archetypes

Hi, to unblock the release I'm changing the version manually now, yes. Would be good to fix though. Cheers, Aljoscha On Mon, 24 Oct 2016 at 20:30 Dan Halperin wrote: > Hmm, this is new in 0.3.0, looks caused by > >

Re: Maven Release Plugin Does Not Update Version of Archetypes

Correct issue link: https://issues.apache.org/jira/browse/BEAM-806 No answers, but looking around. On Mon, Oct 24, 2016 at 10:10 AM, Aljoscha Krettek wrote: > Hi, > are there any Maven mavens who happen to know how > https://issues.apache.org/jira/browse/BEAM-108 can be

Re: A CI Server for Beam?

Hi Sergio - as I mentioned in my email about integration testing sources[1], we'll also need a cluster hosting mechanism for that and I'm checking out some options. In addition to mesos+marathon, I'm checking out kubernetes and docker swarm. I started out excited about mesos, but so far mesos

Re: [DISCUSS] Using Verbs for Transforms

Thanks JB and Jesse. Would something like "MakeDistinct" or "AvoidDuplicate" sound better? I can do the collective changes of the name and the javadoc at one go. Having it documented can be super helpful. On Mon, Oct 24, 2016 at 9:58 AM, Jean-Baptiste Onofré wrote: > It

Re: [DISCUSS] Using Verbs for Transforms

My original thought for this change was that Crunch uses the class name Distinct. SQL also uses the keyword distinct. Maybe the rule should be changed to adjectives or verbs depending on the context. Using a verb to describe this class really doesn't connote what the class does as succinctly as

Re: [ANNOUNCEMENT] New committers!

Now I understand the purpose of your e-mail. It wasn't obvious to me. And it's because I know you that I was surprised  by the e-mail. I think your e-mail was aim to be informative, and I try to provide an informative answer. Regarding Beam, it's large project with a production grade background

Re: [ANNOUNCEMENT] New committers!

My point is that the bar should not be high for committer-ship but not too low as the key thing is valuable contribution. Open mind/discussion, documentation, code, ... are valuable. On the other hand, IMHO, it's also human consideration and behavior. So it's discussion. Not sure I understand

Re: [ANNOUNCEMENT] New committers!

I know how apache projects work. You should know me long enough to know. For people who are less familiar with the process.. One pmc member proposes someone as new committer and the pmc members vote on him/her. Every project of course has a different idea of how high that bar for entry should

Re: [ANNOUNCEMENT] New committers!

Hi Christian, Your e-mail sounds "weird" to me: like other Apache projects, if your contribution is valuable and sustained, then you will deserve committer-ship. It's meritocracy based. Working part time is not a problem, it would make little bit more time to get into. So, just a timing

Re: [DISCUSS] Deferring (pre) combine for merging windows.

@Amit: Yes, Flink is more "what you write is what you get". For example, in Flink we have a Fold function for windows which cannot be efficiently computed with merging windows (it would require using a "group by" window and then folding the iterable). We just don't allow this. For Beam, I think

Re: [ANNOUNCEMENT] New committers!

Congratulations to all three new committers. These are very substantial contributions and all three definitely have earned the committership. As I am only starting to try to help out with beam I wonder how hard it is to become a committer. If I see that Thomas Groh is the number 1 contributor

Re: [ANNOUNCEMENT] New committers!

Congrats and a warm welcome! -Max On Sun, Oct 23, 2016 at 6:02 AM, Robert Bradshaw wrote: > Congrats and welcome to all three of you! > > On Sat, Oct 22, 2016 at 9:02 AM, Thomas Weise wrote: >> Thanks everyone! >> >> >> On Sat, Oct 22, 2016 at

Re: A CI Server for Beam?

Yes. I also have a mesos/marathon to bootstrap a cluster a run test pipelines on it. We are discussing with Jason to use this with our Jenkins. Regards JB ⁣​ On Oct 24, 2016, 08:33, at 08:33, "Sergio Fernández" wrote: >On Mon, Oct 24, 2016 at 8:21 AM, Jean-Baptiste Onofré

Re: A CI Server for Beam?

Yes. I also blogged about this. Basically I used one Maven profile per runner. Same code, different runners. Regards JB ⁣​ On Oct 24, 2016, 08:12, at 08:12, "Sergio Fernández" wrote: >Related, but a bit off-topic: has anybody setup a Bean Pipeline CI >against >the different