Re: Jenkins build is back to normal : beam_Release_NightlySnapshot #131

2016-08-10 Thread Jean-Baptiste Onofré
Good catch. We can exclude heapdump files in rat config. Regards JB On Aug 11, 2016, 06:14, at 06:14, Dan Halperin wrote: >*sigh* > >All I did was clear the workspace and kick the job -- it seems some >intermediate build created a heap dump and then that caused all future >builds to fail on

Re: Jenkins build is back to normal : beam_Release_NightlySnapshot #131

2016-08-10 Thread Dan Halperin
*sigh* All I did was clear the workspace and kick the job -- it seems some intermediate build created a heap dump and then that caused all future builds to fail on Apache RAT. It would be nice to be able to prevent this type of persistent failure from happening in the future. On Wed, Aug 10, 201

Jenkins build is back to normal : beam_Release_NightlySnapshot #131

2016-08-10 Thread Apache Jenkins Server
See

Re: Proposal: Dynamic PIpelineOptions

2016-08-10 Thread Sam McVeety
We can probably build a "real" case around the TextIO boilerplate -- say that a user wants to regularly run a Beam job with a different input path according to the day. TextIO would be modified to support a dynamic value: TextIO.Read.withFilepattern(ValueSupplier); ... and then the pipeline auth

Re: Proposal: Dynamic PIpelineOptions

2016-08-10 Thread Ismaël Mejía
+1 It sounds really nice, (4) is by far the most consistent with the current Options implementation. One extra thing, maybe it is a good idea to sketch a 'real' use case to make the concepts/need more evident. Ismaël On Tue, Aug 9, 2016 at 8:49 PM, Sam McVeety wrote: > Thanks, Amit and JB. Ami

Build failed in Jenkins: beam_Release_NightlySnapshot #130

2016-08-10 Thread Apache Jenkins Server
See Changes: [klk] Cache .m2 directory on Travis-CI [klk] Make StreamingPCollectionViewWriterFn and its data public [fjp] [BEAM-534] Fix dead links in README.md -- Started by timer

Re: [Proposal] Pipelines and their executions naming changes.

2016-08-10 Thread Aljoscha Krettek
Hi, Flink itself allows the user to specify a String when creating a Job, this will be visible in the web dashboard and maybe some other places. This would roughly correspond to the proposed PipelineOptions.pipelineName. An executing job does not have a human-readable name, just an ID that has to b

Re: [PROPOSAL] Website page or Jira to host all current proposal discussion and docs

2016-08-10 Thread Jean-Baptiste Onofré
Great summary. And good idea for a meeting (even if only mailing list counts ;)). Regards JB On Aug 10, 2016, 06:09, at 06:09, Frances Perry wrote: >So to summarize where I think this thread is at -- we'd like to more >clearly lay out the expectations for larger proposals. >- Explain what the