[
https://issues.apache.org/jira/browse/KAFKA-6905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476830#comment-16476830
]
Matthias J. Sax commented on KAFKA-6905:
----------------------------------------
You would edit the file in `kafka` repository (ie, first link) – on release,
`kafka-site` gets updated based on `kafka`.
About HTML: originally it was completely handcrafted but some people started to
use tools that generated some additional markup – it's hard to edit by hand for
those files atm... Sorry for that. We are actually planning to move away from
HTML as it's too cumbersome to maintain in general...
If you think it's too difficult to update the HTML, it would already be helpful
to update the JavaDocs and we can update the HTML later (or actual the non-HTML
after the migration is completed). For this case we would just leave the Jira
open.
> Document that Processor objects can be reused
> ---------------------------------------------
>
> Key: KAFKA-6905
> URL: https://issues.apache.org/jira/browse/KAFKA-6905
> Project: Kafka
> Issue Type: Improvement
> Components: documentation, streams
> Reporter: David Glasser
> Priority: Major
>
> We learned the hard way that Kafka Streams will reuse Processor objects by
> calling init() on them after they've been close()d. This caused a bug in our
> application as we assumed we didn't have to reset all of our Processor's
> state to a proper starting state on init().
> As far as I can tell, this is completely undocumented. The fact that we
> provide Processors to Kafka Streams via a ProcessorSupplier factory rather
> than just by passing in a Processor object made it seem likely that in fact
> Streams was creating Processors from scratch each time it needed a new one.
> The developer guide
> ([https://docs.confluent.io/current/streams/developer-guide/processor-api.html)]
> doesn't even allude to the existence of the close() method, let alone the
> idea that init() may be called after close().
> The Javadocs for Processor.init says: "The framework ensures this is called
> once per processor when the topology that contains it is initialized." I
> personally interpreted that as meaning that it only is ever called once! I
> can see that you could interpret it otherwise, but it's definitely unclear.
> I can send a PR but first want to confirm that this is a doc problem and not
> a bug!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
