Hi I have a topology in production which uses the default kafka spout, I have set this parameter *spoutConfig.forceStartOffsetTime(-1);*
This parameter -1 helps me in such a way that, it consumes from the latest message, and doesn't start reading data from kafka right from the beginning (That would be unnecessary and redundant in my usecase). But in production, whenever a new release goes in, I stop and start the topology which would take a few seconds to minutes. I have been loosing out on some data during the time that the topology is down. How can I avoid this. I have tried running without the ForcedOffsetTime parameter, but that did not work. What am I doing wrong, how can I continue reading from the last offest ? Thanks, Chitra
