[
https://issues.apache.org/jira/browse/KAFKA-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285541#comment-16285541
]
Guozhang Wang commented on KAFKA-3907:
--------------------------------------
Hello Richard, sorry for the late reply. As part of our KIP-159 discussion we
have decided to not postpone adding this API in the higher-level DSL:
http://search-hadoop.com/m/Kafka/uyzND18bJNJ1GDbCZ?subj=+DISCUSS+KIP+159+Introducing+Rich+functions+to+Streams
main since the value of adding this feature v.s. its complexity introduced to
the public API is not clear. If you are looking for some tickets to contribute
to Streams, I'd suggest looking at a few of the following:
KAFKA-6328
KAFKA-6265
KAFKA-3184
> Better support for user-specific committing in the Streams DSL
> --------------------------------------------------------------
>
> Key: KAFKA-3907
> URL: https://issues.apache.org/jira/browse/KAFKA-3907
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Reporter: Guozhang Wang
> Labels: api
>
> Currently for user-specifically committing the current processing state,
> users can make use of the {{ProcessorContext}} object, which is exposed in
> the {{Processor}} API. Other than that, the application will also
> automatically committing the processing state based on the configured
> interval.
> Hence in the Streams DSL, if a user wants to explicitly call {{commit}}, she
> needs to use a {{process(ProcessorSupplier)}} API to get a customized
> processor instance in order to access the {{ProcessorContext}}. We should
> think of a better way to support user-specific committing interfaces inside
> the high-level Streams DSL.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
