Arie

Thank you. I sent a proposal to fix that doc.

See my reply on StackOverflow http://stackoverflow.com/questions/37645138/appengine-mapreduce-fails-with-out-of-memory-during-shuffle-stage . Arie | Ozarov | [email protected] | 415-624-6429 On Mon, Jun 6, 2016 at 2:20 AM, Mayank Bhagya [email protected] wrote: > @ZiglioNZ https://github.com/ZiglioNZ What...

@dlazerka you are correct. Do you want to send a PR to fix it?

1. In the same documentation, a little above, it actually mention that there would be a file per shard. 2. In current implementation if `GoogleCloudStorageOutputWriter` is constructed with `_NO_DUPLICATE=True` in...

@billy1380 great, waiting to see your updates. @eschultink why don't you start the calculation job with and make it depends on a PromisedValue X. pass the X's handle to your...

Yes, the intent was for one to override getJobDisplayName for returning a value which is different from the default. From a user perspective a Job is immutable but this setter...

I don't think any change of job status (or retries) re-persist the job instance. Job information such as status is handled/saved-by JobRecord and the instance is saved by JobInstanceRecord. The...

No recommendation. Follow the path of existing JobSetting handling (shouldn't be too bad).

This is now supported by setting a com.google.appengine.tools.pipeline.BASE_URL system property to the same value as the url-pattern for the PipelineServlet. For example see these [web.xml](https://github.com/GoogleCloudPlatform/appengine-pipelines/blob/master/java/example/war/WEB-INF/web.xml#L13) and [appengine-web.xml](https://github.com/GoogleCloudPlatform/appengine-pipelines/blob/master/java/example/war/WEB-INF/appengine-web.xml#L9).

Just to make it clear. Indeed I am fine with current behavior but adding another way to specify the name via JobSetting as proposed (explicit method override should win) is...