[
https://issues.apache.org/jira/browse/HIVE-20561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618468#comment-16618468
]
Vineet Garg commented on HIVE-20561:
------------------------------------
[~bslim] According to Kafka doc
[LINK|https://kafka.apache.org/10/javadoc/index.html?org/apache/kafka/clients/consumer/KafkaConsumer.html]
position returns the offset of the next record to be fetched, so how is it
different from what we used to do previously?
> Use the position of the Kafka Consumer to track progress instead of Consumer
> Records offsets
> --------------------------------------------------------------------------------------------
>
> Key: HIVE-20561
> URL: https://issues.apache.org/jira/browse/HIVE-20561
> Project: Hive
> Issue Type: Bug
> Affects Versions: 4.0.0
> Reporter: slim bouguerra
> Assignee: slim bouguerra
> Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-20561.2.patch, HIVE-20561.3.patch, HIVE-20561.patch
>
>
> Kafka Partitions with transactional messages (post 0.11) will include commit
> or abort markers which indicate the result of a transaction. The markers are
> not returned to applications, yet have an offset in the log. Therefore the
> end of Stream position can be the offset of a control message.
> This Patch change the way how we keep track of the consumer position by using
> {code} consumer.position(topicP) {code} as oppose to using the offset of the
> consumed messages.
> Also I have done some refactoring to help code readability hopefully.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
