[
https://issues.apache.org/jira/browse/KAFKA-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15439258#comment-15439258
]
Mickael Maison commented on KAFKA-4081:
---------------------------------------
The same happens with 0.10.0.1. Looking at the offset commit logic, the value
of the offset is not checked at all.
It seems some code (ConsumerCoordinator:730) attributes a special meaning to
negative offsets.
One inconsistency I can find is that in the client that commits a negative
offset, calls to committed() will return the negative value whereas in clients
that just fetch the committed offset it returns nothing. This is because when
we commit, it updates the SubscriptionState. This can be seen by using
ConsumerGroupCommand, it shows "unknown" for topics that have a negative offset
committed.
Are there use cases we'd break by forcing offsets to be valid when committed ?
[~ijuma]
> Consumer API consumer new interface commitSyn does not verify the validity of
> offset
> ------------------------------------------------------------------------------------
>
> Key: KAFKA-4081
> URL: https://issues.apache.org/jira/browse/KAFKA-4081
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Affects Versions: 0.9.0.1
> Reporter: lifeng
>
> Consumer API consumer new interface commitSyn synchronization update offset,
> for the illegal offset successful return, illegal offset<0 or offset>hw
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
