[Event] OSCON Call For Proposals Deadline is 1/30

[Griselda Cuevas]

Hi Beam Community,

I just wanted to send a reminder that OSCON's CFP deadline is this 1/30. I
have added a reminder in our brand new events calendar.

You can find more information about the event in their website
. To submit a proposal you
can use this link.


If you're submitting something related to Beam, let us know in this thread.

Enjoy the weekend!
G

Re: [HEADS UP] Preparing Beam 2.3.0

[Jean-Baptiste Onofré]

Hi Reuven,

I gonna bump 3392 and 3087 to 2.4.0. For the PR, yes Eugene did a first round
review, I will work on it now.

We will pretty close !

Thanks !
Regards
JB

On 01/27/2018 05:58 PM, Reuven Lax wrote:
> Seems that 3392 is not a blocker, and neither is 3087. Looks like Eugene is
> already reviewing the PR form BEAM-793.
> 
> Reuven
> 
> On Sat, Jan 27, 2018 at 4:00 AM, Jean-Baptiste Onofré  > wrote:
> 
> Hi guys,
> 
> we still have 7 Jira targeted to 2.3.0.
> 
> For most of them, Ismaël and I are doing the PRs/fixes and we have review 
> in
> progress.
> 
> I'm a little bit concerned by BEAM-3392: it's flagged as blocker but it's
> related to a specific branch. Can you please provide an update asap ?
> 
> However, I didn't have any update for BEAM-3087 (related to the Flink 
> runner).
> Without update soon, I will bump to 2.4.0.
> 
> I would need a review on PR for BEAM-793 (PR #4500). To avoid to break 
> anything
> for existing user, I set the backoff strategy optional, the user has to
> explicitly set to use it.
> 
> I'm waiting a little more before cutting the release (especially for 
> BEAM-3392
> and BEAM-3087). However, I would like to cut the release asap.
> 
> Thanks,
> Regards
> JB
> 
> 
> On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
> > Hi guys,
> >
> > Some days ago, I proposed to start Beam 2.3.0 around January 26th. So, 
> we are
> > few days from this date.
> >
> > As a best effort, can you please in Jira flag the Jira with fix version 
> 2.3.0
> > and blocker for the release. Then, I will know when I can start the
> release process.
> >
> > Thanks !
> >
> > Regards
> > JB
> >
> 
> --
> Jean-Baptiste Onofré
> jbono...@apache.org 
> http://blog.nanthrax.net
> Talend - http://www.talend.com
> 
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [HEADS UP] Preparing Beam 2.3.0

[Reuven Lax]

Seems that 3392 is not a blocker, and neither is 3087. Looks like Eugene is
already reviewing the PR form BEAM-793.

Reuven

On Sat, Jan 27, 2018 at 4:00 AM, Jean-Baptiste Onofré 
wrote:

> Hi guys,
>
> we still have 7 Jira targeted to 2.3.0.
>
> For most of them, Ismaël and I are doing the PRs/fixes and we have review
> in
> progress.
>
> I'm a little bit concerned by BEAM-3392: it's flagged as blocker but it's
> related to a specific branch. Can you please provide an update asap ?
>
> However, I didn't have any update for BEAM-3087 (related to the Flink
> runner).
> Without update soon, I will bump to 2.4.0.
>
> I would need a review on PR for BEAM-793 (PR #4500). To avoid to break
> anything
> for existing user, I set the backoff strategy optional, the user has to
> explicitly set to use it.
>
> I'm waiting a little more before cutting the release (especially for
> BEAM-3392
> and BEAM-3087). However, I would like to cut the release asap.
>
> Thanks,
> Regards
> JB
>
>
> On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
> > Hi guys,
> >
> > Some days ago, I proposed to start Beam 2.3.0 around January 26th. So,
> we are
> > few days from this date.
> >
> > As a best effort, can you please in Jira flag the Jira with fix version
> 2.3.0
> > and blocker for the release. Then, I will know when I can start the
> release process.
> >
> > Thanks !
> >
> > Regards
> > JB
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [HEADS UP] Preparing Beam 2.3.0

[Jean-Baptiste Onofré]

Hi guys,

we still have 7 Jira targeted to 2.3.0.

For most of them, Ismaël and I are doing the PRs/fixes and we have review in
progress.

I'm a little bit concerned by BEAM-3392: it's flagged as blocker but it's
related to a specific branch. Can you please provide an update asap ?

However, I didn't have any update for BEAM-3087 (related to the Flink runner).
Without update soon, I will bump to 2.4.0.

I would need a review on PR for BEAM-793 (PR #4500). To avoid to break anything
for existing user, I set the backoff strategy optional, the user has to
explicitly set to use it.

I'm waiting a little more before cutting the release (especially for BEAM-3392
and BEAM-3087). However, I would like to cut the release asap.

Thanks,
Regards
JB


On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
> Hi guys,
> 
> Some days ago, I proposed to start Beam 2.3.0 around January 26th. So, we are
> few days from this date.
> 
> As a best effort, can you please in Jira flag the Jira with fix version 2.3.0
> and blocker for the release. Then, I will know when I can start the release 
> process.
> 
> Thanks !
> 
> Regards
> JB
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [Proposal] Apache Beam Event's Calendar

[Alexey Romanenko]

+1 for Calendar, excellent idea!

If would be great if it will be on the website as well.

Regards,
Alexey

> On 27 Jan 2018, at 08:10, Ron Gonzalez  wrote:
> 
> +1 to the calendar...
> 
> Thanks,
> Ron
> 
> On Friday, January 26, 2018, 2:27:34 PM PST, Griselda Cuevas 
>  wrote:
> 
> 
> Ok, so given that the proposal seem to have traction I'll proceed as follows: 
> 
> I'll give all PMC members owner rights to the calendar, so they can edit and 
> add events. 
> I'll share the calendar with the dev@ and user@ lists
> I'll investigate how to add the calendar to the Website
> Proposed dynamic to add events to the calendar:
> Anyone can announce an event in the mailing list 
> Anyone with editing rights in the calendar can add a new event
> [For people with Calendar editing rights only] How to add an event to the 
> calendar:
> I'll suggest we use [tags] to classify events in this calendar: 
> [Deadline] -- Use this tag for reminders on deadlines for CFPs, 
> Registrations, etc.
> [USA] -- Use this tag for events in the USA
> [Europe] -- Use this tag for events in Europe
> [APAC] -- Use this tag for events in APAC
> We should add speakers, participants or content directly in the calendar 
> space for details
> Cheers, 
> G
> 
> On 25 January 2018 at 01:35, Ismaël Mejía  > wrote:
> +1
> 
> I think it makes sense to separate it the calendar in two, one for the
> CFPs more interesting for dev@ and one for confirmed events where
> there will be presentations on Beam that concerns more the users
> (user@). It also probably makes sense to include this one in the
> website too.
> 
> 
> 
> 
> On Thu, Jan 25, 2018 at 9:46 AM, Etienne Chauchot  > wrote:
> > +1, great initiative!
> >
> >
> > Le 25/01/2018 à 01:05, Griselda Cuevas a écrit :
> >
> > Hi Beam Community,
> >
> > I've created this public calendar to curate events that the Apache Beam
> > community will attend or is organizing, as well as industry events we should
> > keep in the radar. With this calendar, I want to:
> >
> > Give visibility to the community on what conferences we want to participate
> > in
> > What events is our community organizing
> >
> >
> > My proposal: Share the calendar with the entire dev@ & users@ mailing list
> > and give access as admins to the few folks I know are organizing events to
> > help curate our events.
> >
> > If we get enough votes I'll share the calendar publicly and I'll give access
> > to the other folks.
> >
> > Thanks,
> > G
> >
> >
> 

Build failed in Jenkins: beam_PostRelease_NightlySnapshot #8

[Apache Jenkins Server]

See 


Changes:

[zoy] Increasing BatchElements's max_batch_size to 10K

[tgroh] Retrieve Environments from PTransforms

[kirpichov] [BEAM-3083] Do not call getSchema() and getTable() on every element

[iemejia] Remove unneeded profile for javadoc on Java 8

[iemejia] Remove unneeded explicit Java 8 references on maven-compiler-plugin

[iemejia] Fix doc error on hadoop-input-format ITs after move to Java 8 only 
tests

[iemejia] Remove references to non-existent examples:java8 module in gradle

[iemejia] Remove references to java 7/8 only examples from the README

[iemejia] Remove some comments on Java 7/8 only stuff that don't make sense

[lcwik] [BEAM-2273] Cleanup examples Maven Archetype to copy in a clean state

[XuMingmin] [BEAM-3526] KakfaIO support for finalizeCheckpoint() (#4481)

[kedin] Add Avro dependency to KafkaIO

[lcwik] [Beam-2500] Add S3FileSystem to SDKs/Java/IO

[lcwik] implement serializing AWS credentials provider

[lcwik] fixup! Clarify error message is received from SDK harness

[iemejia] Fix modules that were activated only on Java 8 profile

[iemejia] [BEAM-3275] Fix ValidatesRunner Spark runner after the Kafka update

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on beam4 (beam) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/beam.git # timeout=10
Fetching upstream changes from https://github.com/apache/beam.git
 > git --version # timeout=10
 > git fetch --tags --progress https://github.com/apache/beam.git 
 > +refs/heads/*:refs/remotes/origin/* 
 > +refs/pull/${ghprbPullId}/*:refs/remotes/origin/pr/${ghprbPullId}/*
 > git rev-parse origin/master^{commit} # timeout=10
Checking out Revision b2e92836202ca32e90e9da3e1fd0fa09a0c781a7 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f b2e92836202ca32e90e9da3e1fd0fa09a0c781a7
Commit message: "Merge pull request #4508 from iemejia/fix-java-modules"
 > git rev-list 87670e6f525f3a9e51f6603f072410f86be48447 # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
SPARK_LOCAL_IP=127.0.0.1

[EnvInject] - Variables injected successfully.
[beam_PostRelease_NightlySnapshot] $ /bin/bash -xe 
/tmp/jenkins3375091969846493119.sh
+ cd src/release
+ groovy quickstart-java-direct.groovy
/tmp/jenkins3375091969846493119.sh: line 2: groovy: command not found
Build step 'Execute shell' marked build as failure
Not sending mail to unregistered user ke...@google.com
Not sending mail to unregistered user z...@giggles.nyc.corp.google.com
Not sending mail to unregistered user xuming...@users.noreply.github.com
Not sending mail to unregistered user kirpic...@google.com