[ANNOUNCEMENT] New committers, August 2017 edition!

Please join me and the rest of Beam PMC in welcoming the following contributors as our newest committers. They have significantly contributed to the project in different ways, and we look forward to many more contributions in the future. * Reuven Lax Reuven has been with the project since the very

[ANNOUNCEMENT] New PMC members, August 2017 edition!

Please join me and the rest of Beam PMC in welcoming the following committers as our newest PMC members. They have significantly contributed to the project in different ways, and we look forward to many more contributions in the future. * Ahmet Altay Beyond significant work to drive the Python SDK

Report to the Board, September 2017 edition

We are expected to submit a project report to the ASF Board of Directors ahead of its next meeting. The report is due on Wednesday, 9/13. If interested, please take a look at the draft [1], and comment or contribute content, as appropriate. I'll submit the report sometime in the next 24 hours. Th

Re: Report to the Board, September 2017 edition

Thanks everyone for a super quick turnaround! (The report is now submitted.) On Wed, Sep 13, 2017 at 10:45 AM, Davor Bonaci wrote: > We are expected to submit a project report to the ASF Board of Directors > ahead of its next meeting. The report is due on Wednesday, 9/13. > > I

YOW! Data Conference Sydney 2017

] Time: Tuesday, 9/19, 10:50 am Speaker: Davor Bonaci * Workshop: Data Engineering with Apache Beam [4] Time: Wednesday, 9/20, 9:00 am - 5:00 pm Speaker: Jesse Anderson (with Davor Bonaci) Everybody is welcome -- users and contributors alike! I hope to see many of your there! Davor [1] http

DataWorks Summit Sydney 2017

Apache Beam will be featured at the DataWorks Summit / Hadoop Summit next week in Sydney, Australia [1]. Scheduled events: * Realizing the promise of portable data processing with Apache Beam [2] Time: Thursday, 9/21, 3:10 pm Speaker: Davor Bonaci * Birds-of-a-feather: IoT, Streaming and

Re: DataWorks Summit Sydney 2017

at 11:04 AM, Davor Bonaci wrote: > Apache Beam will be featured at the DataWorks Summit / Hadoop Summit next > week in Sydney, Australia [1]. > > Scheduled events: > * Realizing the promise of portable data processing with Apache Beam [2] > Time: Thursday, 9/21, 3:10 pm &g

A personal update

My dear friends, As many of you have noticed, I’ve been visibly absent from the project for a little while. During this time, a great number of you kept reaching out, and for that I’m deeply humbled and grateful to each and every one of you. I needed some time for personal reflection, which led to

Report to the Board, December 2017 edition

We are expected to submit a project report to the ASF Board of Directors ahead of its next meeting. The report is due on Wednesday, 12/13. If interested, please take a look at the draft [1], and comment or contribute content, as appropriate. I'll submit the report sometime in the next 24 hours. T

Re: Report to the Board, December 2017 edition

wrote: >> >>> LGTM thanks for sharing. >>> >>> >>> >>> On 12 December 2017 at 20:54, Jean-Baptiste Onofré >>> wrote: >>> >>>> It looks good to me. >>>> >>>> Thanks ! >>>> Regards >>>&

Re: Euphoria Java 8 DSL - proposal

Hi David, As JB noted, merging of these two projects is a great idea. If fact, some of us have had those discussions in the past. Legally, nothing particular is strictly necessary as the code seem to already be Apache 2.0 licensed. We don't, however, want to be perceived as making hostile forks, s

Re: Happy new year

Hi everyone -- As we begin the new year, I wanted to send the best wishes in 2018 to everyone in the Beam community -- users, contributors and observers alike! There's so much to be proud of in 2017; including graduation to a top-level project and the availability of the first stable release. Than

[DISCUSS] State of the project

Hi everyone -- Apache Beam was established as a top-level project a year ago (on December 21, to be exact). This first anniversary is a great opportunity for us to look back at the past year, celebrate its successes, learn from any mistakes we have made, and plan for the next 1+ years. I’d like to

Fwd: Google Summer of Code 2018 is coming

This is a great way to grow the community. If you are interested in mentoring students contributing to Beam, please apply! -- Forwarded message -- From: Ulrich Stärk Date: Sun, Jan 21, 2018 at 1:22 PM Subject: Google Summer of Code 2018 is coming To: ment...@community.apache.org

Re: Euphoria Java 8 DSL - proposal

designed to >> "lead the >> programmer", which means, that he >> we'll be only >> offered methods that m

Re: [YouTube channel] Add video: Apache Beam meetup London 2: use case in finance + IO in Beam and Splittable DoFns

(That's not the question for Matthias, it is for the PMC. Thankfully, JB volunteered to help formalize things.) On Fri, Feb 23, 2018 at 7:56 AM, Kenneth Knowles wrote: > +1 to the proposal, and same question as Gris. > > On Wed, Feb 21, 2018 at 9:17 AM, Griselda Cuevas wrote: > >> +1 to the pro

Re: Euphoria Java 8 DSL - proposal

join). >> > >> > Only significant >> difference from >> > Beam is, >> > that we >> > decided not to abst

Re: The Go SDK got accidentally merged - options to deal with the pain

I support leaving things as they stand now -- thanks for finding a good way out of an uncomfortable situation. That said, two things need to happen: (1) SGA needs to be filed asap, per Board feedback in the last report, and (2) releases cannot contain any code from the Go SDK before formally voted

Re: JIRA permissions request

It would be great to spec out "the necessary dashboards, reports, and views", get feedback and agreement, and make it better along the way. AFAIK, requesting this from INFRA should be fine; they can double check what that specific group "all-developers" entails. That said, any tickets filed should

[ANNOUNCEMENT] New Beam chair: Kenneth Knowles

Hi everyone -- It is with great pleasure that I announce that at today's meeting of the Foundation's Board of Directors, the Board has appointed Kenneth Knowles as the second chair of the Apache Beam project. Kenn has served on the PMC since its inception, and is very active and effective in growi

Re: [Proposal] Requesting PMC approval to start planning for Beam Summits 2019

I'd say these matters are generally private between the organizer(s) and the PMC. This thread should continue on the PMC-private mailing list. On Fri, Jan 18, 2019 at 4:06 PM Ahmet Altay wrote: > Thank you Joana. > > Kenn and PMC members could you comment on what needs to be done to move > this

Re: [Proposal] Requesting PMC approval to start planning for Beam Summits 2019

I'm sorry, but certain things require special care. General organizing discussions can proceed on dev@, excluding this specific one. On Sun, Jan 20, 2019 at 8:43 PM Gris Cuevas wrote: > > > On 2019/01/19 16:58:52, Davor Bonaci wrote: > > I'd say these matters are gene

Re: slack @the-asf?

Go for it! Thanks Romain! On Wed, Mar 14, 2018 at 1:35 AM, Romain Manni-Bucau wrote: > Hi guys, > > What do you think to migrate to the standard asf slack? I would make it a > bit more easy to find beam channel IMHO and it would stay consistent with > others. It also allows to auto join for asf

Re: Board report - March '18

Thanks JB for starting the report. If interested, please take a look at the complete draft [1], and comment or contribute content, as appropriate. I'll submit the report sometime in the next 24 hours. Thanks! Davor [1] https://docs.google.com/document/d/1ngoI27CQ25TcxjJlyLBa6Qbj3t7inzf1_20UPN5h

Re: Board report - March '18

t; It looks good to me. >> >> Thanks ! >> >> Regards >> JB >> Le 15 mars 2018, à 08:40, Davor Bonaci a écrit: >>> >>> Thanks JB for starting the report. >>> >>> If interested, please take a look at the complete draft [1], and

[ANNOUCEMENT] New Foundation members!

Now that this is public... please join me in welcoming three newly elected members of the Apache Software Foundation with ties to this community, who were elected during the most recent Members' Meeting. * Ismaël Mejía (Beam PMC) * Josh Wills (Crunch Chair; Beam, DataFu PMC) * Holden Karau (Spar

Re: [PROPOSAL] JIRA notification recipient changes

An INFRA ticket is needed. (As long as the report is automatically a watcher, the change is a strict improvement. If not, it's a strict degradation.) On Tue, Apr 17, 2018 at 1:55 PM, Kenneth Knowles wrote: > Hi all, > > Currently, every touch on a JIRA causes four notifications: > > - all watc

Fwd: Apache Beam - jenkins question

Hi Kamil -- Thanks for reaching out. This is a great question for the dev@ mailing list. You may want to share a little bit more why you need, how long, frequency of updates to the secret, etc. for the community to be aware how things work. Hopefully others on the mailing list can help you by man

Re: Apache Beam - jenkins question

dential is created in Jenkins it should be able to be set as an >> environment variable through the Jenkins job configuration (groovy files in >> $BEAM_ROOT/.test-infra/jenkins). Hope this helps. >> >> Jason >> >> On Thu, Apr 26, 2018 at 8:43 PM Davor Bonaci wrote: >>

Re: Graal instead of docker?

This thread is extremely valuable. It poses hard questions. It strengthens good arguments. It teaches a way of thinking. It gives feedback. I want to thank Romain in particular for driving it, and everyone who has participated thus far. That being said, the exchange has crossed the line on behalf

Re: [VOTE] Go SDK

+1 (binding), with the following caveats: * [before closing the vote] Completion of IP clearance process, as we've been requested. It is easier to do it than having to argue why it is not necessary. * [at any time, possibly later] Figuring out the release mechanics. Great work; across the board!

Re: [VOTE] Go SDK

> > * Robert mentioned that "SGA should have probably already been filed" > in the previous thread. I got the impression that nothing further was > needed. I'll follow up. > Please just follow: http://incubator.apache.org/ip-clearance/. Simple. Quick. Perhaps relevant: I saw some golang license

Re: Missing copyright notices for shaded packages

Thanks for the report! Could you please comment more as to: (1) what artifacts are impacted and where are they distributed, (2) the external dependency being distributed, (3) license and/or term not adhered to, and (4) any proposed fix? Any such information would be helpful in triaging the proble

Re: Missing copyright notices for shaded packages

tice, this list of conditions and the following disclaimer in > the documentation and/or other materials provided with the distribution. > > (4) any proposed fix > > NOTICE file in the jar. > > I am not a lawyer, this is not legal advice. > > On Tue, May 22, 2018 at 2:55

Re: [VOTE] Go SDK

, 2018 at 3:14 PM Robert Bradshaw > wrote: > >> On Tue, May 22, 2018 at 2:42 PM Davor Bonaci wrote: >> >> >>* Robert mentioned that "SGA should have probably already been >> filed" >> in the previous thread. I got the impression that nothing fu

Re: Missing copyright notices for shaded packages

> > jars generated off of current master contain no LICENSE, NOTICE, or other > metadata > We should fix this. This may be an issue. suggested approach of overapproximating >> > The purpose of quoted sentence above ("A part of...") is to qualify when a particular portion applies. It contains extr

Re: [VOTE] Go SDK

ETA: weekend. On Fri, May 25, 2018 at 9:35 AM Henning Rohde wrote: > RESULT: the vote passed with only +1s! Thanks you all for the kind > comments. > > The only pending item is the IP clearance form (draft: > https://web.tresorit.com/l#nUkKlgi3cBYxYAOyhCMXIw >

[ANNOUNCEMENT] New committers, May 2018 edition!

Please join me and the rest of Beam PMC in welcoming the following contributors as our newest committers. They have significantly contributed to the project in different ways, and we look forward to many more contributions in the future. * Griselda Cuevas * Pablo Estrada * Jason Kuster (Apologize

Re: [VOTE] Go SDK

i, May 25, 2018 at 10:26 AM Davor Bonaci wrote: > >> ETA: weekend. >> >> On Fri, May 25, 2018 at 9:35 AM Henning Rohde wrote: >> >>> RESULT: the vote passed with only +1s! Thanks you all for the kind >>> comments. >>> >>> The

Re: Beam Cookbook?

Hi Austin -- It would be great to see this materialize. I've been pursued by publishers a lot in the last year, so I might be able to facilitate introductions if you need them. You'll probably want to have a few sample draft chapters, however. I'm aware of 3 different groups creating related cont

Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2

Please take a peek at LEGAL-288 [1], which I learned about recently in the context of another project. Looks like an issue, requiring a new RC, but I didn't have a chance to look closely. Thanks. Davor [1] https://issues.apache.org/jira/browse/LEGAL-288 On Wed, Jun 20, 2018 at 9:17 AM, Pablo Es

Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2

, it is something that warrants a discussion... On Wed, Jun 20, 2018 at 9:47 AM, Lukasz Cwik wrote: > Davor, please -1 the release if you believe LEGAL-288 applies. > > On Wed, Jun 20, 2018 at 9:37 AM Davor Bonaci wrote: > >> Please take a peek at LEGAL-288 [1], which I learned

Re: Community Examples Repository

> > it makes sense to modularize It certainly does, but somebody just had another proposal to move the website into the main repository ;-). That proposal was also good for ~everyone. Fun times... (I have my opinions, of course, but I'm fine with any approach.) On Wed, Aug 1, 2018 at 4:37 PM, A

Re: Apache Beam Python Wheels Repository

New repository is not a ticket, it is a self-serve thing. That said, you probably want to develop the proposal a bit further, understanding/educating others about the benefits of what you are proposing, any alternatives, why a repository is needed, why the sample repository has Travis CI when ever

Re: [Proposal] Beam Mascot

> > I'd like to get input from the PMC on how this should be pursued (people >> at the foundation who need to be involved, permissions needed, etc.), could >> you advice? >> > Please proceed as you see fit. Nothing is needed, no restrictions. NB: the moment vote passes (and/or the mascot is contri

Re: Please make sure you unincubate

The ASF has not made any public announcement. As far as I understand, that is delayed to the first half of January due to the holidays. That puts us in a awkward state for a few weeks -- I'll reach out to Incubator and ASF folks to clarify how we should be behaving in that time. On Thu, Dec 22, 20

Re: Please make sure you unincubate

The Incubator website has been updated [1, 2], and INFRA-13177 is tracking the infrastructure work [3]. Special thanks to JB and Dan for handling some parts of the work. John, please kindly let us know if you spot something we may have missed. Davor [1] http://incubator.apache.org/projects/ [2]

Re: [DISCUSS] Graduation to a top-level project

announcement is still planned for the second week in January. Davor [1] https://issues.apache.org/jira/browse/INFRA-13177 On Tue, Dec 20, 2016 at 1:22 PM, Davor Bonaci wrote: > A quick update: a meeting of the ASF Board of Directors is scheduled for > later this week, at which the Boa

Re: [DISCUSS] Graduation to a top-level project

t; > On 12/28/2016 07:22 AM, Davor Bonaci wrote: > >> As part of the process, Apache Infra should be reconfiguring our DNS >> records, repository URLs, mailing list addresses, etc. shortly. Please >> expect some instability over the next several days while this is sorted &

Re: [VOTE] Release 0.4.0, release candidate #1

+1 A passing set of Jenkins suites: * https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/6336/ * https://builds.apache.org/job/beam_PostCommit_Java_MavenInstall/2245/ * https://builds.apache.org/job/beam_PostCommit_Java_RunnableOnService_Apex/138/ * https://builds.apache.org/job/beam_P

Re: Hosting data stores for IO Transform testing

Just a quick drive-by comment: how tests are laid out has non-trivial tradeoffs on how/where continuous integration runs, and how results are integrated into the tooling. The current state is certainly not ideal (e.g., due to multiple test executions some links in Jenkins point where they shouldn't

Re: Azure Blob IO for Apache Beam

Hi Saulo, I've responded to your Stack Overflow question, but I can give a few more comments here. Pei (cc'd) is working on this. See this JIRA issue [1], its sub-tasks, and several design documents [2, 3]. It would be awesome to also have native Azure Storage Blob support in Beam that builds on

Apache News Round-up

I stumbled across Apache News Round-up for this week [1], and our own Jean-Baptiste Onofré is noted as one of the top five committers in 2016 with 1,825 commits across all Apache projects. Congratulations JB -- this is awesome! Davor [1] https://blogs.apache.org/foundation/entry/the_apache_news_

Re: Testing Metrics

Sounds like we should do both, right? 1. Test the metrics API without accounting for the various sink types, i.e. > against the SDK. > Metrics API is a runner-independent SDK concept. I'd imagine we'd want to have runner-independent test that interact with the API, outside of any specific transfo

Graduation!

The ASF has publicly announced our graduation! https://blogs.apache.org/foundation/entry/the-apache-software-foundation-announces https://beam.apache.org/blog/2017/01/10/beam-graduates.html Graduation is a recognition of the community that we have built together. I am humbled to be part of

Re: Starter issue

Welcome Tim -- it's great to have you join our community! I found your name in JIRA and assigned the issue to you. Thanks for your (future) contribution. On Wed, Jan 11, 2017 at 11:27 PM, Jean-Baptiste Onofré wrote: > Hi Tim > > What's your Jira id ? > > Thanks > Regards > JB⁣​ > > On Jan 12, 2

Re: On my activity at the project

Thanks Max -- enjoy the time off! Davor On Sun, Jan 15, 2017 at 10:25 AM, Jesse Anderson wrote: > Thanks for all your hard work. > > On Sun, Jan 15, 2017, 10:16 AM Jean-Baptiste Onofré > wrote: > > > Hi Max, > > > > thanks for your commitment and your work on the project. > > > > Enjoy your ti

Re: [DISCUSS] Python SDK status and next steps

+1. I think merging to master would be an awesome next step for the Python SDK. And, thanks for a great summary of the current state, roadmap, and impact to the project as a whole -- awesome! Process-wise, I'd suggest starting a formal vote once this discussion seems to be trending towards a conc

Re: [VOTE] Merge Python SDK to the master branch

[X] +1, Merge python-sdk branch to master after the 0.5.0 release, and release it in the subsequent minor release. On Fri, Jan 20, 2017 at 9:03 AM, Ahmet Altay wrote: > Hi all, > > > Please review the earlier discussion on the status of the Python SDK [1] > and vote on merging the python-sdk br

Re: Runner-provided ValueProviders

Expecting runners to populate, or override, SDK-level pipeline options isn't a great thing, particularly in a scenario that would affect correctness. The main thing is discoverability of a subtle API like this -- there's little chance somebody writing a new runner would stumble across this and do

Re: Subscription to to beam project

Welcome! Please check out the support page [1] with all mailing lists and subscribe links. [1] https://beam.apache.org/get-started/support/ On Sat, Jan 21, 2017 at 11:59 PM, Ritesh Kasat wrote: > Hello, > Please add me to the beam mailing list. > Thanks > Ritesh >

Release 0.5.0

It's been about a month since the last release, so we should start preparing the next one. We have plenty of great content to share with our users! We have a couple of release blocking bugs [1], but they seem to be heading towards a conclusion. Is anybody aware of any other release blocking issues

[ANNOUNCEMENT] New committers, January 2017 edition!

Please join me and the rest of Beam PMC in welcoming the following contributors as our newest committers. They have significantly contributed to the project in different ways, and we look forward to many more contributions in the future. * Stas Levin Stas has contributed across the breadth of the

Re: [VOTE] Apache Beam, version 0.5.0, release candidate #1

It looks good to me, but let's hear Aljoscha's opinion on BEAM-1346. A passing suite of Jenkins jobs: * https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/6870/ * https://builds.apache.org/job/beam_PostCommit_Java_MavenInstall/2474/ * https://builds.apache.org/job/beam_PostCommit_Java_

Re: [DISCUSS] Python SDK status and next steps

Great -- congratulations to everyone who has contributed to the Python SDK! On Mon, Jan 30, 2017 at 11:10 PM, Ahmet Altay wrote: > Hi all, > > This merge is completed. Python SDK is now officially part of the master > branch! Thank you all for the support. Please open an issue, if you notice > a

[VOTE] Apache Beam, version 0.5.0, release candidate #2

Hi everyone, With JB leaving for his vacation, I'll try to push the 0.5.0 release across the finish line. Please review and vote on the release candidate #2 for the version 0.5.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) The comp

Re: [VOTE] Apache Beam, version 0.5.0, release candidate #2

se, since git tags can be changed. Just take that into > account for upcoming releases. > > > On Fri, Feb 3, 2017 at 1:27 AM, Davor Bonaci wrote: > > > Hi everyone, > > With JB leaving for his vacation, I'll try to push the 0.5.0 release > across > > the

[RESULT] [VOTE] Apache Beam, version 0.5.0, release candidate #2

I'm happy to announce that we have unanimously approved this release. There are 5 approving votes, 4 of which are binding: * Davor Bonaci * Sergio Fernández * Dan Halperin * Aljoscha Krettek * Jean-Baptiste Onofré There are no disapproving votes. I'll proceed with the release as stag

Re: BEAM-307(KafkaIO on Kafka 0.10)

This would be a great contribution, Mingmin! As a general rule, we'd like the connector to work with as many versions as possible, with as little code duplication as possible. Slightly orthogonal -- BigtableIO [1] is an example of a connector that separates API portions from the underlying servic

Report to the Board, February 2017 edition

We are expected to submit a project report to the ASF Board of Directors ahead of its next meeting. The report is due on Wednesday, 2/8. This is the second is the series of three monthly reports required for new projects. We'll need to report next month as well. If interested, please take a look

Re: Beam connector development for Hive as a data source

Hi Madhu, Welcome! I suggest subscribing to the dev@ mailing list and using the same email address when sending to the list, to avoid your email being caught in moderation. It would be great to have a connector for Apache Hive. Keep in mind that several folks have expressed interest in using and c

Re: Report to the Board, February 2017 edition

Thanks everyone -- the report has been posted. On Tue, Feb 7, 2017 at 4:05 AM, Jean-Baptiste Onofré wrote: > Hi > > It looks good to me. > > Thanks Davor > Regards > JB > > On Feb 6, 2017, 19:32, at 19:32, Davor Bonaci wrote: > >We are expected to submit a p

Re: [RESULT] [VOTE] Apache Beam, version 0.5.0, release candidate #2

This release is now complete. Thanks to everyone who have helped make this release possible! On Mon, Feb 6, 2017 at 8:36 AM, Davor Bonaci wrote: > I'm happy to announce that we have unanimously approved this release. > > There are 5 approving votes, 4 of which are binding: &g

Re: Better developer instructions for using Maven?

I think Dan's framework of thinking is right -- what is the probability of something finding a real issue, vs. the cost of running that all the time. Obviously, we cannot run *everything* all the time. There's an infinite number of things to run and infinite matrix of configurations. Many tests ar

Re: Beam on Kubernetes

I think these are great ideas for simplifying the getting started experience across runners -- we'd love a contribution in this space! On Mon, Feb 20, 2017 at 12:46 AM, Jean-Baptiste Onofré wrote: > Hi Nitin, > > It sounds like a good candidate for blog or documentation, or even an > example. >

Re: Better developer instructions for using Maven?

(I'm also in favor of not overloading existing flags; they have some meaning/semantics that developers have come to expect.) On Sun, Feb 19, 2017 at 12:34 PM, Jean-Baptiste Onofré wrote: > Thanks Aviem, > > Not sure if we should use skipTests as it really means unit tests and > integration tests

Next major milestone: first stable release

Graduating from incubation was our single, unifying goal for the past year. With graduation now behind us, I think it is worth looking ahead towards the next major milestone: the first stable release. I think the first stable release is the logical next step. It enables the growth of our user comm

Interest in a (virtual) contributor meeting?

In the early days of the project, we have held a few meetings for the initial community to get to know each other. Since then, the community has grown a huge amount, but we haven't organized any get-togethers. I wanted to gauge interest in a potential video conference call in the near future. No s

Re: tf.Transform library for using TensorFlow with Beam

Beam and TensorFlow coming together -- a big deal for us! On Thu, Feb 23, 2017 at 3:49 PM, Ahmet Altay wrote: > Hi all, > > Yesterday, there was an announcement from TensorFlow community about the > new tf.Transform library [1]. It is a library that allows users to define > pre-processing pipeli

Re: Interest in a (virtual) contributor meeting?

7; 2017 2:54 PM,‏ "Aljoscha Krettek" >>> כתב: >>> >>> +1 >>>> >>>> On Wed, 22 Feb 2017 at 10:08 JingsongLee >>>> >>> wrote: >>> >>>> >>>> +1 >>>>> >>>>> >

Re: Release 0.6.0

+1 -- let's get it started! On Mon, Feb 27, 2017 at 2:01 PM, Ahmet Altay wrote: > Hi all, > > It's been about a month since the last release. I would like propose > starting the next release. There are no releasing blocking bugs in JIRA > [1]. Are there any release blocking issues I am missing?

Re: Introduction

Welcome -- it's great to have you! (JIRA and Slack requests done.) On Mon, Feb 27, 2017 at 2:51 PM, Roberto Bentivoglio < roberto.bentivog...@radicalbit.io> wrote: > Hi Everyone, > > I am a big fan of distributed streaming engine and I'm currently working at > Radicalbit. > My colleagues and I a

Re: tf.Transform library for using TensorFlow with Beam

; > # output will contain dicts with 'x_centered', 'y_normalized', and > > > 'x_centered_times_y_normalized' keys > > > # with the expected values, and fn can be used to transform other data > > > using the > > > # statistics (mean, min

Re: Release 0.6.0

Can we please use JIRA to tag potentially release-blocking issues? Anyone can just add a 'Fix Versions' field of an open issue to the next scheduled release -- and it becomes easily visible to everyone in the project. In general, I'm not a fan of blocking releases for new functionality. Rushing ne

Re: Next major milestone: first stable release

Alright -- sounds like we have a consensus to proceed with the first stable release after 0.6.0, targeting end of March / early April. I'll kick off separate threads for specific decisions we need to make. On Thu, Feb 23, 2017 at 6:07 AM, Aljoscha Krettek wrote: > I think we're ready for this! T

Re: Travis retest-this-please magic

It cannot be done at this time. We should really move all Travis coverage into Jenkins and completely deprecate Travis. I know Jason is looking into that ;-) On Wed, Mar 1, 2017 at 3:51 AM, Amit Sela wrote: > Hi all, > > Recently I've encountered PRs where everything was green in Jenkins but >

Re: Travis retest-this-please magic

vis as long as it's not working ? > > On Wed, Mar 1, 2017 at 6:52 PM Davor Bonaci wrote: > > > It cannot be done at this time. > > > > We should really move all Travis coverage into Jenkins and completely > > deprecate Travis. I know Jason is looking into tha

Re: Next major milestone: first stable release

>>> batch in production with some streaming POC or even production use, but >>> batch still takes most of production work. If we give them the same >>> production results, with the Beam API, we can on-board them faster and >>> make >>> it easier for th

First stable release: version designation?

The first stable release is our next major project-wide goal; see discussion in [1]. I've been referring to it as "the first stable release" for a long time, not "1.0.0" or "2.0.0" or "2017" or something else, to make sure we have an unbiased discussion and a consensus-based decision on this matter

Apache Beam (virtual) contributor meeting @ Tue Mar 7, 2017

or Bonaci:mailto:da...@google.com UID:kp637aigav0r5dbo6k7fg8m...@google.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=dev@beam.apache.org;X-NUM-GUESTS=0:mailto:dev@beam.apache.org ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=Davor Bonaci;X-NUM

Re: Apache Beam (virtual) contributor meeting @ Tue Mar 7, 2017

gt; > > Shoot, I can't because I already have another meeting scheduled. Don't > mind > > me, though. Will you also maybe produce a video of the meeting? > > > > On Wed, 1 Mar 2017 at 21:50 Davor Bonaci wrote: > > > > > Hi everyone, > > >

Re: Apache Beam (virtual) contributor meeting @ Tue Mar 7, 2017

Just a remainder that this is happening in about ~22 hours from now. Hope to see all of you there. On Thu, Mar 2, 2017 at 4:22 PM, Davor Bonaci wrote: > I'd prefer not to record the video; just to keep things informal. We'll, > however, keep the notes and share anything that

Re: Apache Beam (virtual) contributor meeting @ Tue Mar 7, 2017

n, Mar 6, 2017 at 7:23 PM Davor Bonaci wrote: > > > Just a remainder that this is happening in about ~22 hours from now. Hope > > to see all of you there. > > > > On Thu, Mar 2, 2017 at 4:22 PM, Davor Bonaci wrote: > > > > > I'd prefer not to record th

Re: First stable release: version designation?

(origins of Beam) was in 1.0.0, in order to > > avoid confusion with users coming to Beam from Dataflow, 2.0.0 could > help. > > > > I have a preference to 1.0.0 anyway, but I would understand starting > > from 2.0.0. > > > > Regards > > JB >

Fwd: Google Summer of Code 2017 Mentor Registration

There was a previous discussion and planning around Beam's involvement with the Summer of Code 2017 -- here's more information on how to get started and formally register as a mentor. Davor -- Forwarded message -- From: Ulrich Stärk Date: Mon, Mar 6, 2017 at 11:39 AM Subject: Goo

Re: found a typographical error in the Beam documentation.

Indeed -- there's a typo on that page. Would you be willing to submit a pull request to our website repository [1] correcting this? Thanks! Davor [1] https://github.com/apache/beam-site On Tue, Mar 7, 2017 at 12:28 AM, 성준영 wrote: > In Beam Documentation - Programming Guide - Applying transfo

Re: found a typographical error in the Beam documentation.

u are > interested, it would be a great honor for me. > > Thanks for the quick answer :) > > > 켜짐 2017년 3월 7일 에서 오후 11:50:58, Davor Bonaci (da...@apache.org) 작성됨: > > Indeed -- there's a typo on that page. > > Would you be willing to submit a pull request to our

Report to the Board, March 2017 edition

We are expected to submit a project report to the ASF Board of Directors ahead of its next meeting. The report is due on Wednesday, 3/8. This is the third is the series of three consecutive monthly reports required for new projects. If interested, please take a look at the draft [1], and comment

Re: Report to the Board, March 2017 edition

The report is now submitted; thanks for the comments and improvements! On Tue, Mar 7, 2017 at 6:14 PM, Davor Bonaci wrote: > We are expected to submit a project report to the ASF Board of Directors > ahead of its next meeting. The report is due on Wednesday, 3/8. > > This is the

Re: Add GitHub topics to Beam repository

We certainly cannot do this ourselves, but it is within the realm of possibility that Apache Infra can assign tags to our GitHub repositories. Looking at the tags that already exist, perhaps we could go with: * apache-beam * big-data * data-processing * data-analysis * data-science * data-analytic

  1   2   >