[
https://issues.apache.org/jira/browse/KAFKA-13641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487519#comment-17487519
]
Mohammad Yousuf Minhaj Zia commented on KAFKA-13641:
----------------------------------------------------
I see. Just wondering what the philosophy of this project is gonna be moving
forward. Is the plan to have type driven semantics? If not I am wondering if I
can create a fork of kafka with only streams as an open source project that is
purely Scala with different type abstractions than ones present.
Although I would love to see DSLv2 with better type semantics, I still really
like DSLv1 and what it has done. Just feel that the line between deterministic
behavior and non-deterministic behavior can be made much much clearer if we go
with the typed route.
> Kafka Streams Scala: Add `Option` to `ValueJoiner` parameters
> -------------------------------------------------------------
>
> Key: KAFKA-13641
> URL: https://issues.apache.org/jira/browse/KAFKA-13641
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Mohammad Yousuf Minhaj Zia
> Priority: Minor
>
> Since `ValueJoiner` right parameter in `leftJoins`, `outerJoins` can be
> nullable, I am wondering if can wrap them around Scala `Option`.
> However, there is also the concern that the left hand side value can be null
> in the case of tombstone messages, in which the `Option` semantics can be
> misleading. I still feel this could be a useful feature in reducing the
> number of `NullPointerExceptions`.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
