Thanks for bringing this up.
We design KStream and KTable to not extending the same base class
intentionally to now allow these classes to be used exchangably or
by design, since their semantics are different for those same-named
methods, for example joins and aggregations, so it is better to enforce
users to think carefully what kind of stream it is applying to.
If you want to "convert" a KStream into a KTable, it should be through
aggregations, and from "KTable" to "KStream" call "toStream" explicitly to
change its semantics.
On Tue, Oct 11, 2016 at 1:08 PM, Ali Akhtar <ali.rac...@gmail.com> wrote:
> They both have a lot of the same methods, and yet they can't be used
> polymorphically because they don't share the same parent interface.
> I think KIterable or something like that should be used as their base
> interface w/ shared methods.