Re: [VOTE] groupId/artifactId naming & layout

The purpose of the vote is to get a consensus actually. We have two options expressed on the mailing list: the current "layout" is good IMHO but all don't agree. So, let's put things on the table and move forward. The vote is a way of discussing. It's not a vote for the release, it's a

Re: Apache Beam for Python

Welcome Python people ;) I know a few people who've been waiting for this one! On Fri, Jun 3, 2016, 19:53 Davor Bonaci wrote: > Welcome Python SDK, as well as Silviu, Charles, Ahmet and Chamikara! > > On Fri, Jun 3, 2016 at 7:07 AM, Jean-Baptiste Onofré

Re: 0.1.0-incubating release

Another consideration for potential future packaging/distribution solutions is how the artifacts line up as files in a flat directory. For that it may be good to have a common prefix in the artifactId and unique artifactId. The name for the source archive (when relying on ASF parent POM) can also

Re: [VOTE] groupId/artifactId naming & layout

This is not a great vote proposal for several reasons: * "Use the current layout" is ambiguous, because it is inconsistent (it is now partly flat and party hierarchical). * Getting the outcome won't move us much closer to the resolution, given that there are several sub-variants in each option. *

Re: Apache Beam for Python

Absolutely ;) On 06/03/2016 03:51 PM, James Malone wrote: Hey Silviu! I think JB is proposing we create a python directory in the sdks directory in the root repository (and modify the configuration files accordingly): https://github.com/apache/incubator-beam/tree/master/sdks This Beam

Re: Apache Beam for Python

I'm more proposing just a folder containing Pythong SDK, not necessary part of the Maven reactor. Regards JB On 06/03/2016 03:34 PM, Silviu Calinoiu wrote: Hi JB, Thanks for the welcome! I come from the Python land so I am not quite familiar with Maven. What do you mean by a Maven module?

Re: Apache Beam for Python

Hey Silviu! I think JB is proposing we create a python directory in the sdks directory in the root repository (and modify the configuration files accordingly): https://github.com/apache/incubator-beam/tree/master/sdks This Beam document here titled "Apache Beam (Incubating): Repository

Re: [VOTE] groupId/artifactId naming & layout

+1 for Option2 On Fri, Jun 3, 2016 at 2:09 PM Jean-Baptiste Onofré wrote: > As said in my previous e-mail, just proposed PR #416. > > Let's start a vote for groupId and artifactId naming. > > [ ] Option1: use the current layout (multiple groupId, artifactId > relative to

Re: 0.1.0-incubating release

Hi Max, I discussed with Davor yesterday. Basically, I proposed: 1. To rename all parent with a prefix (beam-parent, flink-runner-parent, spark-runner-parent, etc). 2. For the groupId, I prefer to use different groupId, it's clearer to me, and it's exactly the usage of the groupId. Some

Re: Serialization for org.apache.beam.sdk.util.WindowedValue$*

Amit, Thanks for this pointer as well, CoderHelpers helps indeed! Thomas On Thu, Jun 2, 2016 at 12:51 PM, Amit Sela wrote: > Oh sorry, of course I meant Thomas Groh in my previous email.. But @Thomas > Weise this example > < >

Re: Serialization for org.apache.beam.sdk.util.WindowedValue$*

Thanks, works like a charm! For such hidden gems there should be a Beam runner newbie guide ;-) Thomas On Thu, Jun 2, 2016 at 11:59 AM, Thomas Groh wrote: > The Beam Model ensures that all PCollections have a Coder; the PCollection > Coder is the standard way to