Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0ABCA200D30 for ; Mon, 30 Oct 2017 23:07:22 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 093CB160BE4; Mon, 30 Oct 2017 22:07:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 25C5A1609D5 for ; Mon, 30 Oct 2017 23:07:20 +0100 (CET) Received: (qmail 51835 invoked by uid 500); 30 Oct 2017 22:07:20 -0000 Mailing-List: contact dev-help@heron.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@heron.incubator.apache.org Delivered-To: mailing list dev@heron.incubator.apache.org Received: (qmail 51818 invoked by uid 99); 30 Oct 2017 22:07:20 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Oct 2017 22:07:20 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 2B5DD180272 for ; Mon, 30 Oct 2017 22:07:19 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.379 X-Spam-Level: ** X-Spam-Status: No, score=2.379 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id j5AFQ05EZoTU for ; Mon, 30 Oct 2017 22:07:13 +0000 (UTC) Received: from mail-lf0-f44.google.com (mail-lf0-f44.google.com [209.85.215.44]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 4A1A05FD89 for ; Mon, 30 Oct 2017 22:07:13 +0000 (UTC) Received: by mail-lf0-f44.google.com with SMTP id b190so16719591lfg.9 for ; Mon, 30 Oct 2017 15:07:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=tx2N3Ii29UWfYA0YvJ/UuB3CS9gmd0s0mHiCzD57KmU=; b=oN7puMevJbCKXZyeDpIWyrEjWYAjPNxiufgVp5TM2q8aFATaRycVTWZIj9DVmwxQOO BC0x01TqqNtqofACjg72hPwxIvwsBju4ZcAuc1p0saObEOMTDYzS9Z/yVc1o5qV4U2K/ wJtWRy5b72sb/33mTvzPN3jDLIrohMr297zMCbf6ssPgt4raIH8bZ9qZnziuy8k8parg tqqpWZL3TLLwSL+YlRor8oyHsRipW4TF6wdcmdi3bFPpzgms5U7zVZZl+DHBKAkPW4CM 2S+ejdE//gz4p0Yr0W8FNkm3tBQwCdRRAPxM2u83y8SQmFELbZo7W9YEz/ME/xjQusOb +kow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=tx2N3Ii29UWfYA0YvJ/UuB3CS9gmd0s0mHiCzD57KmU=; b=dFR6JYmxJZcdUInW3Az243jp22v2kESVqGHt9J8wkHdhyuI45FHD0lzi1zIM8xuVWz PZaNt9VriKHr8dDmxTmphUUXR9gASTWdrH70MUf7va6qmIpL0qfTnPGsd3Rj4tONctEY E9WyVa5JHCKj4V7TkxO603MFA5e70ZitNVBgK+Zma46eJ3wKGpKL+Cz5kO16ldqO8NZj jeom66PUq9Mk6W6MMX4Cy/1Uc+6gyZuEX/ahFTjF4CQfrZLCPMyMWsVKZboE7hKm4fmr tftufRg4g1iikSJAAkV08VWMDdFARaWVNJEmLcevZEYFsZaaJC0CEHH+epuV8rTz/oTi hQBQ== X-Gm-Message-State: AMCzsaVSOilSrW/yZzpKICQGbvUcdNWOI6UnizC9Dno8Q8+9i+vFlaOQ 929UPvt2QIR7ArceHGpia5ucw8SXPxmuNn+3sLz30Q== X-Google-Smtp-Source: ABhQp+S/S2JDSXHTgfaRSrfwxygJybdUQas1FYcMMbeCPNeIOm1/xlcyEpuQQVO8wGx4p17FQoJiwLVl0VCM9fNq7gE= X-Received: by 10.46.67.25 with SMTP id q25mr4194624lja.146.1509401231491; Mon, 30 Oct 2017 15:07:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.146.25 with HTTP; Mon, 30 Oct 2017 15:07:10 -0700 (PDT) In-Reply-To: References: From: Sanjeev Kulkarni Date: Mon, 30 Oct 2017 15:07:10 -0700 Message-ID: Subject: Re: Hello heron community To: dev@heron.incubator.apache.org Content-Type: multipart/alternative; boundary="94eb2c184a663a077e055ccadc0f" archived-at: Mon, 30 Oct 2017 22:07:22 -0000 --94eb2c184a663a077e055ccadc0f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable My initial hunch is that these are different goals and therefore concur with your thought that you could do this in phase 2. On Mon, Oct 30, 2017 at 3:03 PM, Saikat Kanjilal wrote: > The goal is to tie together spark streaming and heron, I could very easil= y > see an architecture where we build topologies in heron to apply business > logic and pump them into time windows with spark streaming where can appl= y > machine learning algorithms inside these windows. > > > Detailed Example: > > > Stock Trading or gamin use case: > > > Heron is used to extract real time data from a gaming or trading client, > > Heron will apply a set of business rules to cleanup this data to fit into > a set of machine learning models > > We need to then figure out how to connect spark streaming to heron, in th= e > case of spark streaming it listens to some tcp or http endpoint so the > objective would be to figure out the bridge between the two worlds. > > > My point here is that if I am going through and building out a scala API > it might make sense to also build a connector to a tech stack entirely > written using scala as a first class citizen. > > > > Let me know your thoughts, we can also push this to phase 2 once the hero= n > scala api is readily available. > > > ________________________________ > From: Sanjeev Kulkarni > Sent: Monday, October 30, 2017 2:54 PM > To: dev@heron.incubator.apache.org > Subject: Re: Hello heron community > > I didn't really get what you meant by 'stream endpoint would be coming fr= om > heron'. Could you please elaborate? Preferably with an example? > > On Mon, Oct 30, 2017 at 2:26 PM, Saikat Kanjilal > wrote: > > > I'm conflicted a bit on 1, here's why I feel like most of our users wou= ld > > want to use the spouts/bolts API who are coming over from Storm or usin= g > > heron for the first time, however the Streamlets interface seems like i= t > > has the right level of abstraction, I think I will start with the > Streamlet > > interface and add in the spout/bolt API as needed. One other thought = I > > had was to figure out an integration plan with spark, to this end the f= it > > between heron and spark would be in using spark streaming where the > stream > > endpoint would be coming from heron, not sure if that should be part of > > this effort or not, what do you guys think? > > > > > > ________________________________ > > From: Sanjeev Kulkarni > > Sent: Monday, October 30, 2017 2:17 PM > > To: dev@heron.incubator.apache.org > > Subject: Re: Hello heron community > > > > I have a couple of questions > > 1. Do you plan on exposing both the low level(spouts/bolts) and the > > streamlet api? Or are you preferring one over another? > > 2. My suggestion would be to start with the Streamlet interface. > Primarily > > because a) Most of scala ml libraries that I've seen tend to operate on > the > > streamlet kind of interface and b) It has a far smaller surface area(i.= e. > > number of interfaces) so might be easy to get something up quickly for > > testing. > > Thanks! > > > > On Mon, Oct 30, 2017 at 2:13 PM, Saikat Kanjilal > > wrote: > > > > > Thanks Sanjeev, I had an initial idea that I wanted to float on the > > list, > > > I was thinking that as part of the initial scala port of the API I'd > like > > > to propose that we use this tool: http://javatoscala.com/ > Java to Scala converter > javatoscala.com > How does it work? Java to Scala converter is created with Play framework > and Scalagen library. I don't want you to see my code. No problem. Java t= o > Scala converter ... > > > > > Java to Scala converter > Java to Scala converter > javatoscala.com > How does it work? Java to Scala converter is created with Play framework > and Scalagen library. I don't want you to see my code. No problem. Java t= o > Scala converter ... > > > > > javatoscala.com > > How does it work? Java to Scala converter is created with Play framewor= k > > and Scalagen library. I don't want you to see my code. No problem. Java > to > > Scala converter ... > > > > > > > > > > > > Java to Scala converter > Java to Scala converter > javatoscala.com > How does it work? Java to Scala converter is created with Play framework > and Scalagen library. I don't want you to see my code. No problem. Java t= o > Scala converter ... > > > > > Java to Scala converter > Java to Scala converter > javatoscala.com > How does it work? Java to Scala converter is created with Play framework > and Scalagen library. I don't want you to see my code. No problem. Java t= o > Scala converter ... > > > > > javatoscala.com > > How does it work? Java to Scala converter is created with Play framewor= k > > and Scalagen library. I don't want you to see my code. No problem. Java > to > > Scala converter ... > > > > > > > > > javatoscala.com > > > How does it work? Java to Scala converter is created with Play > framework > > > and Scalagen library. I don't want you to see my code. No problem. Ja= va > > to > > > Scala converter ... > > > > > > > > > I propose that we use the above tool to do an initial conversion of a= ll > > > the Java functional and oo interfaces and then plug that into the > initial > > > design doc as well as the codebase to get things off the ground. I > have > > > already forked the heron repo and will be doing this off of a child > > branch > > > based on my fork. > > > > > > > > > How does that sound to folks, anyone has strong objections, of course= I > > > fully realize that I will still need to do a lot of work around > > refactoring > > > the code even when using the converter so I'm prepared for that, the > goal > > > in using the converters is to save a bit of time so that manual > > > intervention isnt necessarily needed in designing every interface. > > > > > > Thoughts. > > > > > > ________________________________ > > > From: Sanjeev Kulkarni > > > Sent: Sunday, October 29, 2017 10:18 PM > > > To: dev@heron.incubator.apache.org > > > Subject: Re: Hello heron community > > > > > > Hi Saikat, > > > Welcome to the Heron users group. Your plan of action sounds good to > me. > > A > > > native scala interface would be great for all those scala fans. Eager= ly > > > awaiting design doc. > > > Thanks! > > > > > > On Sun, Oct 29, 2017 at 6:17 PM, Saikat Kanjilal > > > wrote: > > > > > > > Hello Folks, > > > > > > > > I'm interested in taking and driving the following github component > > (this > > > > means design/development/architecture and more). > > > > > > > > > > > > https://github.com/twitter/heron/issues/668 > [https://avatars1.githubusercontent.com/u/367684?s=3D400&v=3D4] github.com/twitter/heron/issues/668> > > Ability to write native scala topologies =C2=B7 Issue #668 =C2=B7 twitter= /heron< > https://github.com/twitter/heron/issues/668> > github.com > Support for Scala Instance and APIs. > > > > > > [https://avatars1.githubusercontent.com/u/367684?s=3D400&v=3D4] > > github.com/twitter/heron/issues/668> > > > > > > Ability to write native scala topologies =C2=B7 Issue #668 =C2=B7 twi= tter/heron< > > > https://github.com/twitter/heron/issues/668> > [https://avatars1.githubusercontent.com/u/367684?s=3D400&v=3D4] github.com/twitter/heron/issues/668> > > Ability to write native scala topologies =C2=B7 Issue #668 =C2=B7 twitter= /heron< > https://github.com/twitter/heron/issues/668> > github.com > Support for Scala Instance and APIs. > > > > > [https://avatars1.githubusercontent.com/u/367684?s=3D400&v=3D4] > github.com/twitter/heron/issues/668> > > > > Ability to write native scala topologies =C2=B7 Issue #668 =C2=B7 twitt= er/heron< > > https://github.com/twitter/heron/issues/668> > [https://avatars1.githubusercontent.com/u/367684?s=3D400&v=3D4] github.com/twitter/heron/issues/668> > > Ability to write native scala topologies =C2=B7 Issue #668 =C2=B7 twitter= /heron< > https://github.com/twitter/heron/issues/668> > github.com > Support for Scala Instance and APIs. > > > > > github.com > > Support for Scala Instance and APIs. > > > > > > > > > github.com > > > Support for Scala Instance and APIs. > > > > > > > > > > > > > > > > > > > > > [https://avatars1.githubusercontent.com/u/367684?v=3D4&s=3D400] > > > github.com/twitter/heron/issues/668> > > > > > > > > Ability to write native scala topologies =C2=B7 Issue #668 ...< > > > > https://github.com/twitter/heron/issues/668> > [https://avatars1.githubusercontent.com/u/367684?s=3D400&v=3D4] github.com/twitter/heron/issues/668> > > Ability to write native scala topologies =C2=B7 Issue #668 =C2=B7 twitter= /heron< > https://github.com/twitter/heron/issues/668> > github.com > Support for Scala Instance and APIs. > > > > > [https://avatars1.githubusercontent.com/u/367684?s=3D400&v=3D4] > github.com/twitter/heron/issues/668> > > > > Ability to write native scala topologies =C2=B7 Issue #668 =C2=B7 twitt= er/heron< > > https://github.com/twitter/heron/issues/668> > [https://avatars1.githubusercontent.com/u/367684?s=3D400&v=3D4] github.com/twitter/heron/issues/668> > > Ability to write native scala topologies =C2=B7 Issue #668 =C2=B7 twitter= /heron< > https://github.com/twitter/heron/issues/668> > github.com > Support for Scala Instance and APIs. > > > > > github.com > > Support for Scala Instance and APIs. > > > > > > > > > [https://avatars1.githubusercontent.com/u/367684?s=3D400&v=3D4] > > github.com/twitter/heron/issues/668> > > > > > > Ability to write native scala topologies =C2=B7 Issue #668 =C2=B7 twi= tter/heron< > > > https://github.com/twitter/heron/issues/668> > [https://avatars1.githubusercontent.com/u/367684?s=3D400&v=3D4] github.com/twitter/heron/issues/668> > > Ability to write native scala topologies =C2=B7 Issue #668 =C2=B7 twitter= /heron< > https://github.com/twitter/heron/issues/668> > github.com > Support for Scala Instance and APIs. > > > > > [https://avatars1.githubusercontent.com/u/367684?s=3D400&v=3D4] > github.com/twitter/heron/issues/668> > > > > Ability to write native scala topologies =C2=B7 Issue #668 =C2=B7 twitt= er/heron< > > https://github.com/twitter/heron/issues/668> > [https://avatars1.githubusercontent.com/u/367684?s=3D400&v=3D4] github.com/twitter/heron/issues/668> > > Ability to write native scala topologies =C2=B7 Issue #668 =C2=B7 twitter= /heron< > https://github.com/twitter/heron/issues/668> > github.com > Support for Scala Instance and APIs. > > > > > github.com > > Support for Scala Instance and APIs. > > > > > > > > > github.com > > > Support for Scala Instance and APIs. > > > > > > > > > > > > > github.com > > > > heron - Heron is a realtime, distributed, fault-tolerant stream > > > processing > > > > engine from Twitter > > > > > > > > > > > > > > > > > > > > I've joined the heron slack channel as recommended and am ready to > > start > > > > by creating a master JIRA issue to track this if not already done, = I > > > wanted > > > > some guidance from a committer or two to help guide me a bit take > care > > of > > > > at he administrative details and how to get this kicked off the > ground. > > > My > > > > background includes working on apache reef codebase as well as > dabbling > > > in > > > > apache mahout and apache flume as well as storm and various > nosql/graph > > > > databases. Looking forward to being part of the community. > > > > > > > > > > > > > > > > The rough plan of action in my mind so you know: > > > > > > > > 1) Review heron architecture and codebase in detail > > > > > > > > 2) Create an umbrella JIRA with the first series of tasks > > > > > > > > 3) Come up with a design doc > > > > > > > > 4) Build the interfaces > > > > > > > > 5) Add more dev tasks to JIRA > > > > > > > > 6) Drive the implementation > > > > > > > > > > > > Thanks in advance for your help. > > > > > > > > > > > > > > --94eb2c184a663a077e055ccadc0f--