This page is meant as a template for writing a KIP. To create a KIP choose Tools->Copy on this page and modify with your content and replace the heading with the next KIP number and a description of your issue. Replace anything in italics with your own description.

Status

Current state: "Under DiscussionAccepted"

Discussion thread: here [Change the link from the KIP proposal email archive to your own email thread]

Github PR: here

Jira: 

Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

Motivation

...

should be:

...

Public Interfaces

KStream.process

Proposed Changes

We want to make sure that we always have a serde for all Materialized, Serialized, Joined, Consumed and Produced.
For that we can make use of the implicit parameters in Scala.

Public Interfaces

Add of the following:

org.apache.kafka.streams.scala.kstream.Materialized
org.apache.kafka.streams.scala.kstream.Serialized
org.apache.kafka.streams.scala.kstream.Joined
org.apache.kafka.streams.scala.kstream.Consumed
org.apache.kafka.streams.scala.kstream.Produced

Proposed Changes

Add of helper functions to create Materialized, Serialized, Joined, Consumed and Produced with serdes implicitly given so that we are sure to not miss any.def process(processorSupplier: => Processor[K, V], stateStoreNames: String*)

Compatibility, Deprecation, and Migration Plan

Overload and deprecate, then remove the deprecated.

Rejected Alternatives

If there are alternative ways of accomplishing the same thing, what were they? The purpose of this section is to motivate why the design is the way it is and not some other way.NA