Github user iBuddha commented on the pull request:
https://github.com/apache/storm/pull/331#issuecomment-79609715
@d2r Sorry, my description behind lastest offset is not corrent. It
should be currentOffset, currentOffset could be other offset besides
latest. But currentOffset could
Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/331#issuecomment-75586158
@iBuddha, thanks. I merged this to master.
Post your name if you would like it in the contributors list along with
your github id.
If you would like attribution in
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/331
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/331#issuecomment-75583629
Created [STORM-685](https://issues.apache.org/jira/browse/STORM-685) for
this.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user Parth-Brahmbhatt commented on the pull request:
https://github.com/apache/storm/pull/331#issuecomment-72499073
+1.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
GitHub user vesense opened a pull request:
https://github.com/apache/storm/pull/405
Update PartitionManager.java
fix bug [STORM-643] KafkaUtils repeat fetch messages which offset is out
of range
You can merge this pull request into a Git repository by running:
$ git pull
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/331#issuecomment-67103228
+1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
