Hi Damian - We could. But in case the user wants to use both Scala and Java APIs (may be for some mixed mode application), won't that be confusing ? She will have to do something like ..
import o.a.k.s.scala.{KStream => KStreamS} to rename Scala imports or the other way round for imported Java classes. regards. On Fri, Mar 16, 2018 at 9:07 PM, Damian Guy <damian....@gmail.com> wrote: > Hi Debasish, > > Thanks for the KIP - will be a great addition to streams. I've only had a > quick scan, but seeing as the Scala classes are going to be in their own > package could we drop the S at the end of the class names? > > Thanks, > Damian > > > On Fri, 16 Mar 2018 at 15:25 Debasish Ghosh <debasish.gh...@lightbend.com> > wrote: > > > Hi - > > > > A new KIP, KIP-270 is up for discussion: > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 270+-+A+Scala+Wrapper+Library+for+Kafka+Streams > > > > The relevant JIRA issue: https://issues.apache.org/ > jira/browse/KAFKA-6670 > > > > The library as proposed in the KIP has been implemented at > > https://github.com/lightbend/kafka-streams-scala and the current release > > is > > 0.2.0 ( > > https://github.com/lightbend/kafka-streams-scala/releases/tag/v0.2.0). > > We at Lightbend has been using it since quite some time now. > > > > regards. > > > > -- > > Debasish Ghosh > > Principal Engineer > > > > Twitter: @debasishg > > Blog: http://debasishg.blogspot.com > > Code: https://github.com/debasishg > > > -- Debasish Ghosh Principal Engineer Twitter: @debasishg Blog: http://debasishg.blogspot.com Code: https://github.com/debasishg