[02/27] storm git commit: STORM-563. Kafka Spout doesn't pick up from the beginning of the queue unless forceFromStart specified.

[pt...@apache.org]

STORM-563. Kafka Spout doesn't pick up from the beginning of the queue unless forceFromStart specified.


Project: http://git-wip-us.apache.org/repos/asf/storm/repo
Commit: http://git-wip-us.apache.org/repos/asf/storm/commit/847fc1cf
Tree: http://git-wip-us.apache.org/repos/asf/storm/tree/847fc1cf
Diff: http://git-wip-us.apache.org/repos/asf/storm/diff/847fc1cf

Branch: refs/heads/0.10.x-branch
Commit: 847fc1cf6dcdc139f6f91a191a40a4dae1e97238
Parents: 28d40a4
Author: Sriharsha Chintalapani <ma...@harsha.io>
Authored: Tue Mar 31 20:21:29 2015 -0700
Committer: P. Taylor Goetz <pt...@gmail.com>
Committed: Fri May 15 14:57:34 2015 -0400

----------------------------------------------------------------------
 external/storm-kafka/README.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/storm/blob/847fc1cf/external/storm-kafka/README.md
----------------------------------------------------------------------
diff --git a/external/storm-kafka/README.md b/external/storm-kafka/README.md
index 8a98c0c..a841880 100644
--- a/external/storm-kafka/README.md
+++ b/external/storm-kafka/README.md
@@ -124,10 +124,12 @@ OpaqueTridentKafkaSpout spout = new OpaqueTridentKafkaSpout(spoutConf);
 
 As shown in the above KafkaConfig properties , user can control where in the topic they can start reading by setting **KafkaConfig.startOffsetTime.**
 
-There are two options **kafka.api.OffsetRequest.EarliestTime()** which makes the KafkaSpout to read from the begining of the topic and 
-**kafka.api.OffsetRequest.LatestTime()** which starts at the end of the topic (or any new messsages that are being written to the topic).
+These are the options
+1. **kafka.api.OffsetRequest.EarliestTime()  or -2 (value returned by EarliestTime())** which makes the KafkaSpout to read from the begining of the topic 
+2. **kafka.api.OffsetRequest.LatestTime() or -1 (value returned by LatestTime())** which starts at the end of the topic ,any new messsages that are being written to the topic
+3. **System.time.currentTimeMillis()**
 
-When user first deploys a KakfaSpout based topology they can use one of the above two options. As the topology runs 
+When user first deploys a KakfaSpout based topology they can use one of the above options. As the topology runs 
 KafkaSpout keeps track of the offsets its reading and writes these offset information under **SpoutConfig.zkRoot+ "/" + SpoutConfig.id**
 Incase of failures it recovers from the last written offset from zookeeper.