on Spark, doh

On Thu, May 11, 2017 at 5:45 PM, Jason Kuster <jasonkus...@google.com>
wrote:

> Just validated a decently-sized wordcount on a YARN cluster successfully.
>
> On Thu, May 11, 2017 at 3:51 PM, Kenneth Knowles <k...@google.com.invalid>
> wrote:
>
>> I gave the archetype-based quickstart a try on as many runners and
>> configurations as I could manage today, mostly embedded and YARN.
>>
>> There are some issues (filed and added to the doc) that may have to do
>> with
>> my setup, but may not. I'd prefer the runner maintainers / system experts
>> try these on their more realistic setups.
>>
>> On Thu, May 11, 2017 at 3:28 PM, Thomas Groh <tg...@google.com.invalid>
>> wrote:
>>
>> > I'm making sure the direct runner plays nice in a variety of scenarios
>> > (primarily the game examples, at the moment. Been a couple of hours and
>> > still going strong in streaming)
>> >
>> > On Thu, May 11, 2017 at 3:09 PM, Dan Halperin
>> <dhalp...@google.com.invalid
>> > >
>> > wrote:
>> >
>> > > I'm focusing on:
>> > >
>> > > * user reported bugs (Avro, TextIO, MongoDb)
>> > > * the actual Apache Release criteria (licensing, dependencies, etc.)
>> > >
>> > > On Thu, May 11, 2017 at 3:04 PM, Lukasz Cwik <lc...@google.com.invalid
>> >
>> > > wrote:
>> > >
>> > > > I have been trying out various Python scenarios on Windows.
>> > > >
>> > > > On Thu, May 11, 2017 at 3:01 PM, Jason Kuster <
>> > > > jasonkus...@google.com.invalid> wrote:
>> > > >
>> > > > > I'll try to get wordcount running against a Spark cluster.
>> > > > >
>> > > > > On Wed, May 10, 2017 at 10:32 PM, Davor Bonaci <da...@apache.org>
>> > > wrote:
>> > > > >
>> > > > > > Just a quick remainder to consider to consider contributing
>> here.
>> > > > > >
>> > > > > > We are now at 6 criteria -- thanks!
>> > > > > >
>> > > > > > On Tue, May 9, 2017 at 2:29 AM, Aljoscha Krettek <
>> > > aljos...@apache.org>
>> > > > > > wrote:
>> > > > > >
>> > > > > > > Thanks for starting this document!
>> > > > > > >
>> > > > > > > I added a criterion and also verified it on the current RC.
>> > > > > > >
>> > > > > > > Best,
>> > > > > > > Aljoscha
>> > > > > > >
>> > > > > > > > On 8. May 2017, at 22:48, Davor Bonaci <da...@apache.org>
>> > wrote:
>> > > > > > > >
>> > > > > > > > Based on the process previously discussed [1], I've seeded
>> the
>> > > > > > acceptance
>> > > > > > > > criteria document [2].
>> > > > > > > >
>> > > > > > > > Please consider contributing to this effort by:
>> > > > > > > > * proposing additional acceptance criteria, and/or
>> > > > > > > > * supporting criteria proposed by others, and/or
>> > > > > > > > * validating a criteria.
>> > > > > > > >
>> > > > > > > > Please note that acceptance criteria shouldn't been too
>> deep or
>> > > too
>> > > > > > broad
>> > > > > > > > -- those are covered by automated tests and hackathon we had
>> > > > earlier.
>> > > > > > > This
>> > > > > > > > should be "sanity-check"-type of criteria: simple,
>> > surface-level
>> > > > > > things.
>> > > > > > > >
>> > > > > > > > If you discover issues while validating a criteria, please:
>> > > > > > > > * file a new JIRA issue, tag it as Fix Versions: “2.0.0”,
>> and
>> > > > > > > > * post on the dev@ mailing list on the thread about that
>> > > specific
>> > > > > > > release
>> > > > > > > > candidate.
>> > > > > > > >
>> > > > > > > > Thanks!
>> > > > > > > >
>> > > > > > > > Davor
>> > > > > > > >
>> > > > > > > > [1]
>> > > > > > > > https://lists.apache.org/thread.html/
>> > > > 37caa5a94cec1405638410857f489d
>> > > > > > > 7cf7fa12bbe3c36e9925b2d6e2@%3Cdev.beam.apache.org%3E
>> > > > > > > > [2]
>> > > > > > > > https://docs.google.com/document/d/
>> > > 1XwojJ4Mj3wSlnBO1YlBs51P8kuGyg
>> > > > > > > YRj2lrNrqmAUvo/
>> > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > > --
>> > > > > -------
>> > > > > Jason Kuster
>> > > > > Apache Beam / Google Cloud Dataflow
>> > > > >
>> > > >
>> > >
>> >
>>
>
>
>
> --
> -------
> Jason Kuster
> Apache Beam / Google Cloud Dataflow
>



-- 
-------
Jason Kuster
Apache Beam / Google Cloud Dataflow

Reply via email to