You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2015/10/28 15:20:27 UTC

[jira] [Resolved] (STORM-697) Support for Emitting Kafka Message Offset and Partition

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

Jungtaek Lim resolved STORM-697.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 0.11.0

https://issues.apache.org/jira/browse/STORM-697

Thanks for the great work, [~mjtieman55].
I merged into master.
Sorry for really late (over half of the year) to review and merge.
Thanks for your patience.

> Support for Emitting Kafka Message Offset and Partition
> -------------------------------------------------------
>
>                 Key: STORM-697
>                 URL: https://issues.apache.org/jira/browse/STORM-697
>             Project: Apache Storm
>          Issue Type: Improvement
>          Components: storm-kafka
>            Reporter: Matthew Tieman
>            Assignee: Matthew Tieman
>             Fix For: 0.11.0
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> It would be nice expose the offset and partition of messages consumed from Kafka to the Scheme generating the Tuples. This is useful for auditing/replaying data from arbitrary points on a Kafka topic. There are a few ways to accomplish this. 
> One is to define a new scheme, say MessageAndMetadataScheme, and add another case in KafkaUtils.generateTuples to determine if the config's schema is an instance of MessageAndMetadataScheme.
> Another is to overload KafkaUtils.generateTuples to accept and instance of MessageAndRealOffset. Next, add a flag to SpoutConfig indicating that the scheme should accept a byte array of MessageAndRealOffset, this flag will be used to determine which generateTuples method to call.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)