Return-Path: X-Original-To: apmail-streams-dev-archive@minotaur.apache.org Delivered-To: apmail-streams-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C6285178EA for ; Fri, 13 Feb 2015 15:49:46 +0000 (UTC) Received: (qmail 82088 invoked by uid 500); 13 Feb 2015 15:49:12 -0000 Delivered-To: apmail-streams-dev-archive@streams.apache.org Received: (qmail 81994 invoked by uid 500); 13 Feb 2015 15:49:12 -0000 Mailing-List: contact dev-help@streams.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@streams.incubator.apache.org Delivered-To: mailing list dev@streams.incubator.apache.org Received: (qmail 81672 invoked by uid 99); 13 Feb 2015 15:49:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Feb 2015 15:49:12 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 13 Feb 2015 15:49:08 +0000 Received: (qmail 80942 invoked by uid 99); 13 Feb 2015 15:48:48 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Feb 2015 15:48:48 +0000 Received: from mail-yh0-f54.google.com (mail-yh0-f54.google.com [209.85.213.54]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id E8A631A0031 for ; Fri, 13 Feb 2015 15:48:47 +0000 (UTC) Received: by mail-yh0-f54.google.com with SMTP id z6so8432258yhz.13 for ; Fri, 13 Feb 2015 07:48:47 -0800 (PST) X-Gm-Message-State: ALoCoQnzRafv0/Dx9iTfAgzFto4CmmC8Nyzfb3JL8JWuhSvMUpmETXNPsWI7UdDhxIr3rmDDoxcg MIME-Version: 1.0 X-Received: by 10.236.7.136 with SMTP id 8mr9597122yhp.46.1423842526985; Fri, 13 Feb 2015 07:48:46 -0800 (PST) Received: by 10.170.54.73 with HTTP; Fri, 13 Feb 2015 07:48:46 -0800 (PST) X-Originating-IP: [70.113.76.84] Date: Fri, 13 Feb 2015 09:48:46 -0600 Message-ID: Subject: [VOTE] Official library of examples From: Steve Blackmon To: "dev@streams.incubator.apache.org" Content-Type: multipart/alternative; boundary=001a11c1ea6c099e67050efa2c89 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c1ea6c099e67050efa2c89 Content-Type: text/plain; charset=UTF-8 Please vote in favor of provisioning a new empty git repo named streams-examples associated with this project. The discussion below will inform the initial commit, of a basic pom hierarchy and README documenting the guidelines for adding examples. Examples that meet community standards will be welcome from all Apache contributors. Vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Steve Blackmon sblackmon@apache.org On Thu, Feb 12, 2015 at 10:11 AM, Matt Franklin wrote: > On Thu Feb 12 2015 at 11:09:35 AM Robert Douglas < > robert.baker.douglas@gmail.com> wrote: > > > Hey Steve, I think this is a great idea. Streams has a ton of use cases > and > > I think to a new user, they can be a bit daunting. I'd be happy to help > > shore up some of the examples. > > > > I would recommend having infra setup a separate git repository and adding > modules to that from scratch, rather than importing them from another > repository. > > > > > > -- Robert > > > > On Wed, Feb 11, 2015 at 9:53 AM, Steve Blackmon > > wrote: > > > > > Reviving an old discussion: > > > > > > I propose that we create an official streams-examples repository in the > > > apache git repository with the following characteristics: > > > > > > - maven multi-level multi-module project > > > - reference streams-project as parent > > > - first level : runtime (local, dropwizard, pig, storm, etc...) > > > - below, individual examples modules built upon that runtime. > > > > > > Each example would: > > > > > > - Contain a primary class which uses a StreamsBuilder to launch an > > > example stream, or set of complementary streams. > > > - Alternatively, contain a script suitable for execution within a > > > specific runtime (pig/spark shell for example) > > > - Optionally, contain processors and utility classes suited to a > > > specific purpose within > > > - Optionally, override the behavior of providers, processors, > utility > > > classes from the core project to achieve a specific purpose > > > - Contain a configuration class which declares all required and > > optional > > > configuration > > > - Contain a README.md conforming to a template TBD, describing what > > the > > > example does > > > - Contain at least one example configuration in src/main/resources > and > > > in README.md > > > - Contain a machine readable graph definition (dot or suitable > > > alternative) and png version visible in README.md > > > - Contain integration test(s) demonstrating that a small input set > > > traverses the stream, resulting in expected outputs and (optionally) > > > properly handled exceptions. > > > - Describe requirements for a successful deployment and execution in > > > README.md. > > > - Build an executable uber-jar > > > - Build an executable docker image > > > > > > https://github.com/steveblackmon/streams-examples is a collection of > > > modules that conform in varying degrees to this pattern. Less > organized > > > and less tested than I'm proposing, but containing code & poms that are > > > minimal, readable, and useful "out-of-the-box". I'll commit to > > increasing > > > the quality of 5-10 of them and submitting them to > > > > > > Anyone agree this is a good idea? Have concerns? Want to help? > > > > > > Steve Blackmon > > > sblackmon@apache.org > > > > > > --001a11c1ea6c099e67050efa2c89--