You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@heron.apache.org by Saikat Kanjilal <sx...@hotmail.com> on 2017/11/11 13:17:00 UTC
[Discuss] First cut of design doc ready for scala port of heron
Hello Heron community,
I have created the first cut of an API design doc for the Scala port for heron here:
https://docs.google.com/document/d/1vIL4hVC4SwYU5YkP9cFSn6poJ0M1_XROrB-Kl50xDs4/edit
API Design for Heron Scala Port<https://docs.google.com/document/d/1vIL4hVC4SwYU5YkP9cFSn6poJ0M1_XROrB-Kl50xDs4/edit>
docs.google.com
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 will consist of a set of interfaces , I will build the codebase after every interface conversion so that the design actually reflects the port which b...
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 Java implementations to the upper level scala traits. Do let me know your thoughts either either on this thread or the doc or finally the slackchannel.
Thanks in advance for your help.
Re: [Discuss] First cut of design doc ready for scala port of heron
Posted by Saikat Kanjilal <sx...@hotmail.com>.
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 <hu...@gmail.com>> wrote:
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 <ka...@streaml.io>>
wrote:
Thanks Saikat. Let us give a few days for comments to come in.
On Sat, Nov 11, 2017 at 5:17 AM, Saikat Kanjilal <sx...@hotmail.com>>
wrote:
Hello Heron community,
I have created the first cut of an API design doc for the Scala port for
heron here:
https://docs.google.com/document/d/1vIL4hVC4SwYU5YkP9cFSn6poJ0M1_
XROrB-Kl50xDs4/edit
API Design for Heron Scala Port<https://docs.google.com/document/d/
1vIL4hVC4SwYU5YkP9cFSn6poJ0M1_XROrB-Kl50xDs4/edit>
docs.google.com<http://docs.google.com>
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
will
consist of a set of interfaces , I will build the codebase after every
interface conversion so that the design actually reflects the port which
b...
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
Java
implementations to the upper level scala traits. Do let me know your
thoughts either either on this thread or the doc or finally the
slackchannel.
Thanks in advance for your help.
Re: [Discuss] First cut of design doc ready for scala port of heron
Posted by FatJ Love <hu...@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 <ka...@streaml.io>
wrote:
> Thanks Saikat. Let us give a few days for comments to come in.
>
> On Sat, Nov 11, 2017 at 5:17 AM, Saikat Kanjilal <sx...@hotmail.com>
> wrote:
>
> > Hello Heron community,
> >
> > I have created the first cut of an API design doc for the Scala port for
> > heron here:
> >
> >
> > https://docs.google.com/document/d/1vIL4hVC4SwYU5YkP9cFSn6poJ0M1_
> > XROrB-Kl50xDs4/edit
> >
> > API Design for Heron Scala Port<https://docs.google.com/document/d/
> > 1vIL4hVC4SwYU5YkP9cFSn6poJ0M1_XROrB-Kl50xDs4/edit>
> > docs.google.com
> > 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
> will
> > consist of a set of interfaces , I will build the codebase after every
> > interface conversion so that the design actually reflects the port which
> > b...
> >
> >
> > 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
> Java
> > implementations to the upper level scala traits. Do let me know your
> > thoughts either either on this thread or the doc or finally the
> > slackchannel.
> >
> >
> > Thanks in advance for your help.
> >
>
Re: [Discuss] First cut of design doc ready for scala port of heron
Posted by Karthik Ramasamy <ka...@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 <sx...@hotmail.com>
wrote:
> Hello Heron community,
>
> I have created the first cut of an API design doc for the Scala port for
> heron here:
>
>
> https://docs.google.com/document/d/1vIL4hVC4SwYU5YkP9cFSn6poJ0M1_
> XROrB-Kl50xDs4/edit
>
> API Design for Heron Scala Port<https://docs.google.com/document/d/
> 1vIL4hVC4SwYU5YkP9cFSn6poJ0M1_XROrB-Kl50xDs4/edit>
> docs.google.com
> 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 will
> consist of a set of interfaces , I will build the codebase after every
> interface conversion so that the design actually reflects the port which
> b...
>
>
> 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 Java
> implementations to the upper level scala traits. Do let me know your
> thoughts either either on this thread or the doc or finally the
> slackchannel.
>
>
> Thanks in advance for your help.
>