[
https://issues.apache.org/jira/browse/KAFKA-17939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17944404#comment-17944404
]
Matthias J. Sax commented on KAFKA-17939:
-----------------------------------------
I think this "leak" was introduced many years back... As Sophie already said,
it's unclear why internal code is not in an "internals" package – the rule
about JavaDocs makes it hard to reason about what is public and what is not, by
just looking at the code. And the fact that we, KS maintainers did leak these
classes, proves the point. Well, water down the bridge.
Using additional tooling is always welcome, but again, it seems much simpler to
just use an easy to reason about package structure (or do both)? But it does
not help us to resolve this ticket.
I agree, that we need a KIP to make `Bytes` and `Time` public API, and I agree
that it makes sense to check all interfaces/classed of `o.a.k.common.utils` if
they might be used already. [~siddharthadevineni] are you interested in driving
a KIP?
> Kafka Streams API exposes org.apache.kafka.common.utils.Bytes which is not
> part of the public API
> -------------------------------------------------------------------------------------------------
>
> Key: KAFKA-17939
> URL: https://issues.apache.org/jira/browse/KAFKA-17939
> Project: Kafka
> Issue Type: Task
> Components: streams
> Reporter: Mickael Maison
> Priority: Major
>
> Quite a few public API classes/interfaces in org.apache.kafka.streams and
> org.apache.kafka.streams.kstreams expose the
> org.apache.kafka.common.utils.Bytes class. However Bytes is not part of the
> public API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
