On Sep 12, 2013, at 20:55 , phanichaitanya <pvempaty....@gmail.com> wrote: > Apologies again. But here is another try : > > I want to make sure that documents that are indexed are committed in say an > hour. I agree that if you pass commitWithIn params and the like will make > sure of that based on the time configurations we set. But, I want to make > sure that the document is really committed within whatever time we set using > commitWithIn. > > It's a question asking for proof that Solr commits within that time if we > add commitWithIn parameter to the configuration. > > That is about commitWithIn parameter option that you suggested. > > Now is there a way to explicitly get all the documents that are committed > when a hard commit request is issued ? This might not make sense but we are > pondered with that question. >
If you have a timestamp field that defaults to NOW, you could do queries for a single document (q=*), ranked by descending timestamp. If you're feeding constantly, and run these queries regularly, you should be able to get some sort of feel for the latency in the system.
