Re: Schema-Aware PCollections revisited

Le 30 janv. 2018 01:09, "Reuven Lax" a écrit : On Mon, Jan 29, 2018 at 12:17 PM, Romain Manni-Bucau wrote: > Hi > > I have some questions on this: how hierarchic schemas would work? Seems it > is not really supported by the ecosystem (out of custom

Detecting resources to stage

I wanted to bring back to the community that there are two competing PRs on how classloaders are being used to detect which resources needed to run a pipeline: * https://github.com/apache/beam/pull/4497 * https://github.com/apache/beam/pull/4514 PR/4497 uses the fact that in JDK 9 doesn't use a

Re: Schema-Aware PCollections revisited

Hi I have some questions on this: how hierarchic schemas would work? Seems it is not really supported by the ecosystem (out of custom stuff) :(. How would it integrate smoothly with other generic record types - N bridges? Concretely I wonder if using json API couldnt be beneficial: json-p is a

Re: [HEADS UP] Preparing Beam 2.3.0

Good point Kenn. I will do the list of what we need to do a release with gradle. Regards JB On 01/29/2018 07:31 PM, Kenneth Knowles wrote: > I'd also love if we can use the notes to keep track of what needs to be done > for > Gradle. > > On Mon, Jan 29, 2018 at 10:29 AM, Jean-Baptiste Onofré

Re: [HEADS UP] Preparing Beam 2.3.0

I'd also love if we can use the notes to keep track of what needs to be done for Gradle. On Mon, Jan 29, 2018 at 10:29 AM, Jean-Baptiste Onofré wrote: > Sure, I will ;) > > First steps: > > 0. Validate the build: mvn clean install -Prelease,sign > 0bis. dryRun on the release:

Re: [HEADS UP] Preparing Beam 2.3.0

Great. I'm interested in any pain points in the process, and steps we can automate. Can you keep a rough log of issues you run into? On Mon, Jan 29, 2018 at 10:16 AM, Jean-Baptiste Onofré wrote: > We are now ready for the release. I'm starting the process. > > Thanks again

Re: [HEADS UP] Preparing Beam 2.3.0

We are now ready for the release. I'm starting the process. Thanks again for your help and support ! Regards JB On 01/29/2018 02:22 PM, Jean-Baptiste Onofré wrote: > Hi, > > new update (and I hope the last one ;)): > > - BEAM-3551 has been reviewed and merged. This Jira is fixed for 2.3.0. >

Re: [HEADS UP] Preparing Beam 2.3.0

Awesome, thanks Ahmet ! It's what I thought, but wanted to have team agreement ;) Regards JB On 01/29/2018 06:19 PM, Ahmet Altay wrote: > I moved BEAM-3559 out of 2.3.0, it is not targeted for this release. > > On Mon, Jan 29, 2018 at 5:22 AM, Jean-Baptiste Onofré

Re: [PROPOSAL] Add a blog post for every new release

+1. Release notes from jira may be hard to digest for people outside the project. A short summary for may be really helpful for those considering Beam or loosely following the project to get an understanding of what is happening. It also presents a good opportunity share progress externally,

Re: [PROPOSAL] Add a blog post for every new release

+1 I like the idea and agree with adding it to the release guide. Even a very short post the length of an email is nice. We could have a template to make it very easy. On Mon, Jan 29, 2018 at 8:02 AM, Romain Manni-Bucau wrote: > +1 to have it as a best effort - most of

Re: [PROPOSAL] Add a blog post for every new release

+1 to have it as a best effort - most of projects do. But as JB said, if it slows down the release motivation it shouldn't be enforced but just encouraged. A good solution Ismael is you take this responsability for the coming releases after the release manager is done with the annoucement. This

Re: [DISCUSS] State of the project: Culture and governance

Hello again, Some comments inlined: JB, > 1. The code of conduct is the one from Apache. Yes I am not necessarily saying that we need a new one, I am just saying that we need to make this explicit, not sure everybody is aware of it https://www.apache.org/foundation/policies/conduct.html > 2.

Re: [PROPOSAL] Add a blog post for every new release

Hi Ismaël The idea is good, but the post should be pretty short. Let me explain: - We will have a release every two months now, so, some releases might be lighter than others, and it's normal - the Jira Release Notes already provides lot of details For instance, in Apache projects like Karaf,

Build failed in Jenkins: beam_PostRelease_NightlySnapshot #10

See Changes: [aromanenko.dev] [BEAM-3539] BigtableIO.Write javadoc of some methods is incorrect [rangadi] Remove an unused test dependency in KafkaIO. [jbonofre] Typo fix in MinimalWordCount