kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neha Narkhede (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-183) Expose offset vector to the consumer
Date Tue, 12 Jun 2012 00:06:43 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Neha Narkhede updated KAFKA-183:
--------------------------------

    Issue Type: Sub-task  (was: New Feature)
        Parent: KAFKA-364
    
> Expose offset vector to the consumer
> ------------------------------------
>
>                 Key: KAFKA-183
>                 URL: https://issues.apache.org/jira/browse/KAFKA-183
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Jay Kreps
>            Assignee: Jay Kreps
>
> We should enable consumers to save their position themselves. This would be useful for
consumers that need to store consumed data so they can store the data and the position together,
this gives a poor man's "transactionality" since any data loss on the consumer will also rewind
the position to the previous position so the two are always in sync.
> Two ways to do this:
> 1. Add an OffsetStorage interface and have the zk storage implement this. The user can
override this by providing an OffsetStorage implementation of their own to change how values
are stored.
> 2. Make commit() return the position offset vector and add a setPosition(List<Long>)
method to initialize the position.
> Let's figure out any potential problems with this, and work out the best approach.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message