heron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Saikat Kanjilal <sxk1...@hotmail.com>
Subject Re: [Discuss] First cut of design doc ready for scala port of heron
Date Sat, 11 Nov 2017 21:17:25 GMT
Yes that’s the next large effort after this,the decision to port the streamlet API came from
an earlier discussion thread on this topic.  Let’s see how the experience goes with this
porting and as the next adventure we can then tackle the low level API, one step at a time

Sent from my iPhone

On Nov 11, 2017, at 12:50 PM, FatJ Love <huijun.wu.2010@gmail.com<mailto:huijun.wu.2010@gmail.com>>

It seems the proposed Scala API is from Java streamlet API. Will we port
Java low level API to Scala as well ?

On Sat, Nov 11, 2017 at 10:48 AM, Karthik Ramasamy <karthik@streaml.io<mailto:karthik@streaml.io>>

Thanks Saikat. Let us give a few days for comments to come in.

On Sat, Nov 11, 2017 at 5:17 AM, Saikat Kanjilal <sxk1969@hotmail.com<mailto:sxk1969@hotmail.com>>

Hello Heron community,

I have created the first cut of an API design doc for the Scala port for
heron here:


API Design for Heron Scala Port<https://docs.google.com/document/d/
API Design for Heron Scala Port Introduction This document will outline
all of the api’s associated with the scala port for heron. The design
consist of a set of interfaces , I will build the codebase after every
interface conversion so that the design actually reflects the port which

The doc has some high level objectives and a simple list of the Java
interfaces and code corresponding to the Scala port.  Please review in
detail and add feedback, for each addition of the Scala trait or I went
ahead and just did a basic compile of the code and from there added the
trait to the design doc.    I want to nail down this design doc first
before any more deeper incisions into the code.  As a bare minimum I have
cleaned up each of the traits to have the correct package and removed
unneeded classes like JavaToScalaConversions where appropriate and added
the appropriate license on the top of each trait.  Once the feedback is
collected we can go about this two ways, have a discussion thread on the
apache list to vet the APIs and in parallel I will tie the underlying
implementations to the upper level scala traits.   Do let me know your
thoughts either either on this thread or the doc or finally the

Thanks in advance for your help.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message