[
https://issues.apache.org/jira/browse/KAFKA-10688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17228465#comment-17228465
]
Bruno Cadonna commented on KAFKA-10688:
---------------------------------------
Maybe I misunderstood your previous comment.
In your proposal in 1) and 2) aren't you proposing to reset repartition topics
by using the global policy?
When would a repartition topic not have a valid committed offset after an
offset was committed for the first time (i.e. first commit after a fresh start
of the Streams application)?
Is not the fact that an repartitition topic does not have a valid committed
offset enough to throw a fatal error? Why should we reset the repartition
topics in point 1) and 2) in your proposal?
> Handle accidental truncation of repartition topics as exceptional failure
> -------------------------------------------------------------------------
>
> Key: KAFKA-10688
> URL: https://issues.apache.org/jira/browse/KAFKA-10688
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Guozhang Wang
> Assignee: Guozhang Wang
> Priority: Major
>
> Today we always handle InvalidOffsetException from the main consumer by the
> resetting policy assuming they are for source topics. But repartition topics
> are also source topics and should never be truncated and hence cause
> InvalidOffsetException.
> We should differentiate these repartition topics from external source topics
> and treat the InvalidOffsetException from repartition topics as fatal and
> close the whole application.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
