[
https://issues.apache.org/jira/browse/KAFKA-7654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16694960#comment-16694960
]
Matthias J. Sax commented on KAFKA-7654:
----------------------------------------
Thanks for sharing your thoughts. This are all valid points. The only thing I
disagree is
{quote}In this fluent style I don't think the end-user cares much about which
builder classes are returned as long as the IDE suggests valid methods. The
main point is discoverability.
{quote}
I thought so too, but we already have intermediate representation like
`KGroupedStream` etc and people stumble over it... I was also surprised but it
does indeed affect user more than one might think. (But I guess this is a minor
point in the discussion.)
In the end, as you agreed, it's a trade-off. As a library, it's always tricky
to be opinionated about things, for example, how people serialize their data...
I am personally not convinced yet (but I am just one voice of many) that the
proposal would improve the API (even if there are loop holes in the API, that
would benefit to be improved). Nevertheless, if you want to suggest a change to
the community, feel free to start a KIP
([https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals]).
Or maybe [~bbejeck], [~vvcephei], or [~guozhang] want to share their thoughts
first?
> Relax requirements on serializing-only methods.
> -----------------------------------------------
>
> Key: KAFKA-7654
> URL: https://issues.apache.org/jira/browse/KAFKA-7654
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Bruno Bieth
> Priority: Major
>
> Methods such as KStream#to shouldn't require a Produced as only the
> serializing part is ever used.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
