Re: Adding back PipelineRunner#apply method

This style of method doesn't fit with the current approach of pipeline construction, where the PipelineRunner need not be specified until the pipeline is run; as such, the runner can't observe the construction of the Pipeline, as it may not exist during the construction of the Pipeline. On Tue,

Re: Adding back PipelineRunner#apply method

Hi Thomas, Does it mean future Pipeline implementations would allow applications to set the runner after a pipeline has been constructed? Thanks, Shen On Tue, Aug 15, 2017 at 12:36 PM, Thomas Groh wrote: > This style of method doesn't fit with the current approach of

Re: Adding back PipelineRunner#apply method

On Tue, Aug 15, 2017 at 10:21 AM, Shen Li wrote: > Hi Thomas, > > Does it mean future Pipeline implementations would allow applications to > set the runner after a pipeline has been constructed? Correct, that's the intent. > > Thanks, > Shen > > On Tue, Aug 15, 2017 at

Hello from a newbie to the data world living in the city by the bay!

Hi Beam community, I’m Griselda (Gris) Cuevas and I’m very excited to join the community, I’m looking forward to learning awesome things from you and to getting the chance to collaborate on great initiatives. I’m currently working at Google and I’m studying a masters in operations research and

Re: Adding back PipelineRunner#apply method

thank you! Shen On Tue, Aug 15, 2017 at 1:29 PM, Robert Bradshaw < rober...@google.com.invalid> wrote: > On Tue, Aug 15, 2017 at 10:21 AM, Shen Li wrote: > > Hi Thomas, > > > > Does it mean future Pipeline implementations would allow applications to > > set the runner

Re: Hello from a newbie to the data world living in the city by the bay!

Welcome both of you! Some helpful starting points: - Contribution guide [1] - Unassigned starter issues in JIRA [2] Ahmet [1] https://beam.apache.org/contribute/contribution-guide/ [2]

Re: Adding back PipelineRunner#apply method

In general, no - but the implementation of PAssertionSite exemplifies the approach. I guess it could be useful to make this a general beam feature and remember it for all transforms. It would probably be best to implement inside Pipeline.apply(). On Tue, Aug 15, 2017, 7:02 AM Shen Li

Re: Policy for stale PRs

Yea, I think we will need a policy like this eventually, or face unbounded old PRs. I would be OK with closing after 60 or 30 days of silence, too, since all that is needed is a reply, plus they can always re-open. What have other projects done? On Mon, Aug 14, 2017 at 5:29 PM, Ted Yu

Re: Adding back PipelineRunner#apply method

... And remember it and make available inside PCollection (which application produced this collection). On Tue, Aug 15, 2017, 8:39 AM Eugene Kirpichov wrote: > In general, no - but the implementation of PAssertionSite exemplifies the > approach. I guess it could be useful

Re: [ANNOUNCEMENT] New committers, August 2017 edition!

Congrats! Excellent works! On Mon, Aug 14, 2017 at 11:50 PM, Aviem Zur wrote: > Congrats! > > On Mon, Aug 14, 2017 at 6:43 PM Tyler Akidau > wrote: > > > Congrats and thanks all around! > > > > On Sat, Aug 12, 2017 at 12:09 AM Aljoscha Krettek

Re: [PROPOSAL] "Requires deterministic input"

On Tue, Aug 15, 2017 at 1:59 PM, Robert Bradshaw < rober...@google.com.invalid> wrote: > On Sat, Aug 12, 2017 at 1:13 AM, Reuven Lax > wrote: > > On Fri, Aug 11, 2017 at 10:52 PM, Robert Bradshaw < > >> The question here is whether the ordering is part of the "content"

Re: [PROPOSAL] "Requires deterministic input"

On Tue, Aug 15, 2017 at 2:14 PM, Reuven Lax wrote: > On Tue, Aug 15, 2017 at 1:59 PM, Robert Bradshaw < > rober...@google.com.invalid> wrote: > >> On Sat, Aug 12, 2017 at 1:13 AM, Reuven Lax >> wrote: >> > On Fri, Aug 11, 2017 at 10:52 PM,

Re: [PROPOSAL] "Requires deterministic input"

On Sat, Aug 12, 2017 at 1:13 AM, Reuven Lax wrote: > On Fri, Aug 11, 2017 at 10:52 PM, Robert Bradshaw < >> The question here is whether the ordering is part of the "content" of >> an iterable. > > My initial instinct was to say yes - but maybe it should not be until

Re: Hello from a newbie to the data world living in the city by the bay!

Hello Beam community, I am also a new member, and I feel a little better knowing that there others on the same boat:) My name is Justin and I work as a full stack engineer for Neustar, a marketing analytics company in San Diego. Over the past few weeks I have been getting more familiar with Beam

Re: [VOTE] Release 2.1.0, release candidate #3

Hey all, Seems like we're missing one more affirmative vote from a PMC member (so far we have JB and Ahmet) to proceed with the release. On Mon, Aug 14, 2017 at 9:30 AM Ahmet Altay wrote: > On Mon, Aug 14, 2017 at 6:32 AM, Ismaël Mejía wrote: > > >

Re: [ANNOUNCEMENT] New committers, August 2017 edition!

Congrats! On Mon, Aug 14, 2017 at 6:43 PM Tyler Akidau wrote: > Congrats and thanks all around! > > On Sat, Aug 12, 2017 at 12:09 AM Aljoscha Krettek > wrote: > > > Congrats, everyone! It's well deserved. > > > > Best, > > Aljoscha > > > > > On

Jenkins build is back to stable : beam_Release_NightlySnapshot #504

See

Re: Adding back PipelineRunner#apply method

Hi Eugene, Thanks for sharing the info. That PAssertionSite tracks where an assertion error occurred. Do you know if it is possible to get the class name and line number where a PTransform was added? Thanks, Shen On Mon, Aug 14, 2017 at 10:54 PM, Eugene Kirpichov < kirpic...@google.com.invalid>